is cleared to ?0? when the received slave address is the same as the value set at the i2c0ar or when a general call is received (all 8-bit data are ?0? after a start condi tion). although sbi0cr2 can be set to ?1? by the program, the is not cleared to ?0? when it is written ?0?. 8.3.3.9 serial bus interface operation mode selection sbi0cr2 is used to specify the serial bus interface operation mode. set sbi0cr2 to ?10? when the device is to be used in i 2 c bus mode after confirming pin condition of serial bus interface to ?h?. switch to port mode after confirming a bus is free. 8.3.3.10 arbitration lost detection monitor since more than one master device can exist simultaneously on the bus in i 2 c bus mode, a bus arbitra- tion procedure has been implemented in order to guarantee the integrity of transferred data. data on the sda line is used for i 2 c bus arbitration. the following shows an example of a bus arbitration procedure when two master devices exist simulta- neously on the bus. master a and master b output the same data until point ?a?. after master a outputs ?l? and master b, ?h?, the sda line of the bus is wired-and and the sda line is pulled down to the low level by master a. when the scl line of the bus is pul led up at point b, the slave device reads the data on the sda line, that is, data in master a. a data tr ansmitted from master b becomes invalid. the state in master b is called ?arbitration lost?. master b device which loses arbitra tion releases the internal sda output in order not to affect data transmitted from other masters with arbitration. when more than one master sends the same data at the first word, arbitration occurs continuou sly after the second word. figure 8-7 arbitration lost the tmp91fu62 compares the levels on the bus?s s da line with those of the internal sda output on the rising edge of the scl line. if the levels do not match, arbitration is lost and sbi0sr is set to ?1?. ab scl pin internal sda output (master a) internal sda output (master b) sda pin internal sda output becomes 1 after arbitration has been lost.
page 154 2007-10-10 tmp91fu62 when sbi0sr is set to ?1?, sbi0sr are cleared to ?00? and the mode is switched to slave receiver mode. thus, clock output is sto pped in data transfer after setting = ?1?. sbi0sr is cleared to ?0 ? when data is written to or read from sbi0dbr or when data is written to sbi0cr2. figure 8-8 example of when tmp91fu62 is a master de vice b (d7a = d7b, d6a = d6b) 8.3.3.11 slave address match detection monitor sbi0sr is set to ?1? in sl ave mode, in address recognition mode (e.g., when i2c0ar = ?0?), when a general call is recei ved, or when a slave address matches the value set in i2c0ar. when i2c0ar = ?1?, sbi0sr is set to ?1? after the first word of data has been received. sbi0sr is cleared to ?0? when data is written to or read from the data buffer register sbi0dbr. 8.3.3.12 general call detection monitor sbi0sr is set to ?1? in slave mode, when a general call is r eceived (all 8-bit received data is ?0? after a start condition). sbi0sr is cleared to ?0? when a start condition or stop condi- tion is detected on the bus. 8.3.3.13 last received bit monitor the sda line value stored at the rising edge of the scl line is set to the sbi0sr. in the acknowledge mode, immediately after an intsbi interrup t request is generated, an acknowledge signal is read by reading the conten ts of the sbi0sr. 8.3.3.14 software reset function the software reset function is used to initialize th e sbi circuit, when sbi is locked by external noises, etc. an internal reset signal pulse can be generated by setting sbi0cr2 to ?10? and ?01?. this initializes the sbi circuit internally. all control registers and status registers are initialized as well. sbi0cr1 is automatically set to ?1? after the sbi circuit has been initialized. note: if the software reset is executed, operation selection is reset, and its mode is set to port mode from i 2 c mode. d7a d6a d5a d4a d7b d6b d3a d2a d1a d6a'd7a' d5a' d4a' d0a 1 2 3 4 1 2 3 4 5 6 7 8 9 1 2 3 4 internal scl output accessed to sbi0dbr or sbi0cr2 internal sda output internal scl output internal sda output master a master b stop the clock pulse keep internal sda output to high level as losing arbitration
page 155 2007-10-10 tmp91fu62 8.3.3.15 serial bus interface data buffer register (sbi0dbr) the received data can be read and transferred data can be written by readi ng or writing the sbi0dbr. in the master mode, after the start condition is generated the slave address and the direction bit are set in this register. 8.3.3.16 i 2 cbus address register (i2c0ar) i2c0ar is used to set the slave address when the tmp91fu62 func tions as a slave device. the slave address output from the master device is recognized by setting the i2c0ar to ?0?. the data format is the addressing format. when the slave address is not recognized at the = ?1?, the data format is the free data format. 8.3.3.17 setting register for idle2 mode operation (sbi0br0) sbi0br0 is the register setting operat ion/stop during idle2 mode. therefore, setting is necessary before th e halt instruction is executed. 8.3.4 data transfer in i 2 c bus mode 8.3.4.1 device initialization set the sbi0cr1, clear bits 2 to 0 and 4 in the sbi0cr1 to ?0?. set a slave address and th e ( = ?0? when an ad dressing format) to the i2c0ar. for specifying the default setting to a slave receive r mode, clear ?0? to the sbi0cr2, set ?1? to the , ? 10? to the , and write ?0? to bit 1, 0. 76543210 sbi0cr1 x x x 0 x 0 0 0 set acknowledge and scl clock. i2c0ar x x x x x x x 0 set slave address and address recognition mode. sbi0cr2 00011000 set to slave receiver mode. note: x: don?t care
page 156 2007-10-10 tmp91fu62 8.3.4.2 start condition and slave address generation (1) master mode in the master mode, the star t condition and the slave address are generated as follows. check a bus free status (when = ?0?). set the sbi0cr1 to ?1? (acknowledge mode ) and specify a slave address and a direction bit to be transmitted to the sbi0dbr. when sbi0cr2 = ?0?, the start condition are generated by writing ?1? to sbi0cr2. subsequently to the start condition, nine clocks are output from the scl pin. while eight clocks are output, th e slave address and the direction bit wh ich are set to the sbi0dbr. at the 9th clock, the sda line is releas ed and the acknowledge signal is received from the slave device. an intsbi0 interrupt request occurs at the falling edge of the 9th clock. the is cleared to ?0?. in the master mode, the scl pin is pulled dow n to the low level while is ?0?. when an interrupt request occurs, the is changed according to the direction bit only when an acknowl- edge signal is returned from the slave device. in intsbi0 interrupt routine intclr <-- 0x30 ; clear the interrupt request process end of interrupt (2) slave mode in the slave mode, the start conditio n and the slave address are received. after the start condition is receive d from the master device, while eight clocks are output from the scl pin, the slave address and the direction bit whic h are output from the mast er device are received. when a general call or the same address as the slave address set in i2c0ar is received, the sda line is pulled down to the low level at the 9th clock, and the acknowledge signal is output. an intsbi0 interrupt request occurs on the falling edge of the 9th clock. the is cleared to ?0?. in slave mode the scl line is pulled down to the low level while the = ?0?. setting in main routine 76543210 reg sbi0sr reg reg. 0x20 if reg 0x00 wait until bus is free. then sbi0cr1 x x x 1 x 0 0 0 set to acknowledgement mode. sbi0dbr x x x x x x x x set slave address and direction bit. sbi0cr2 11111000 generate start condition.
page 157 2007-10-10 tmp91fu62 figure 8-9 start condition gener ation and slave address transfer 8.3.4.3 1-word data transfer check the by the intsbi0 inte rrupt process after the 1-word da ta transfer is completed, and determine whether the mode is a master or slave. (1) if = ?1? (master mode) check the and determine whether th e mode is a transmitter or receiver. (a) when the = ?1? (transmitter mode) check the . when is ?1?, a receive r does not request da ta. implement the pro- cess to generate a stop condition (refer to below) and terminate data transfer. when the is ?0?, the receiver requests ne w data. when the next transmitted data is 8 bits, write the transmitted data to sbi0dbr. wh en the next transmitted data is other than 8 bits, set the and write the transmitted data to sbi0dbr. after written the data, becomes ?1?, a seri al clock pulse is generated for transferring a new 1 word of data from the scl pin, and then the 1-word data is transmitted. after the data is transmitted, an intsbi interrupt request occurs. the becomes ?0? and the scl line is pulled down to the low level. if the data to be transferred is mo re than one word in lengt h, repeat the procedure from the checking above. if mst = 0 then shift to the process when slave mode if trx = 0 then shift to the process when receiver mode. if lrb = 0 then shift to the process that generates stop condition. 76543210 sbi0cr1 0 0 0 1 x x x x set the bit number of transmit and ack. sbi0dbr xxxxxxxx write the transmit data. end of interrupt note: x: don?t care a6 a5 2 3 4 5 6 7 8 9 a4 a3 a2 a1 a0 ack r/w 1 scl pin sda pin intsbi interrupt request start condition slave address + direction bit output of master output of slave acknowledge signal from a slave device
page 158 2007-10-10 tmp91fu62 figure 8-10 example in which = ?000? and = ?1? in transmitter mode (b) when the is ?0? (receiver mode) when the next transmitted data is other than 8 bits, set and read the received data from sbi0dbr to release the scl line (data which is read immediately after a slave address is sent is undefined). after the data is read, becomes ?1?. serial clock pulse for transferring new 1 word of data is defined scl and outputs ?l? level from sda pin with acknowledge timing. an intsbi0 interrupt request then occurs and the becomes ?0?, then the tmp91fu62 pulls down the scl pin to the low level. the tmp91fu62 outputs a clock pulse for 1 word of data tran sfer and the acknowledge signal each ti me that received data is read from the sbi0dbr. figure 8-11 example of when = ?000?, = ?1 ? in receiver mode in order to terminate the transmission of da ta to a transmitter, cl ear to ?0? before reading data which is 1 word before the last da ta to be received. the last data word does not generate a clock pulse as the acknowledge signal. after the data has been transmitted and an interrupt request has been generated, set to ?001? and read the data. the tmp91fu62 generates a clock pulse for an 1-bit data transfer. since the master device is a receiver, the sda line on the bus remains high. the transmitter interprets the high signal as an ack signal. the receiver indicates to the tran smitter that data transfer is complete. after the one data bit has been received a nd an interrupt request been generated, the tmp91fu62 generates a stop condition and terminates data transfer. d7 d6 2 3 4 5 6 7 8 9 d5 d4 d3 d2 d1 d0 ack 1 scl pin write to sbi0dbr sda pin intsbi interrupt request output from master output from slave acknowledge signal from a receiver d7 d6 2 3 4 5 6 7 8 9 d5 d4 d3 d2 d1 ack 4d7 d0 1 scl pin read sbi0dbr sda pin intsbi interrupt request output from master output from slave acknowledge signal to a
page 159 2007-10-10 tmp91fu62 figure 8-12 termination of data transfer in mast er receiver mode (2) if = 0 (slave mode) in the slave mode the tmp91fu62 operates either in normal slave mode or in slave mode after losing arbitration. in the slave mode, an intsbi0 interrupt reques t occurs when the tmp91fu62 receives a slave address or a general call from the master device, or when a general call is received and data transfer is complete, or after matching received address. in the master mode, the tmp91fu62 operates in a slave mode if it detects losing arbitr ation. an intsbi0 interrupt request occurs when a word data transfer terminates af ter losing arbitration. when an in tsbi0 interrupt request occurs the is cleared to ?0? and the scl pin is pulled down to the low level. either reading/writing from/ to the sbi0dbr or setting the to ?1 ? will release the scl pin after taking t low time. check the sbi0sr, , , and and implements processes according to conditions listed in the next table. example: in case receive data n times intsbi0 interrupt (after transmitting data) 76543210 sbi0cr1 x x x x x x x x set the bit number of receive data and ack. reg. sbi0dbr load the dummy data. end of interrupt intsbi0 interrupt (receive data of 1st to (n 2) th) 76543210 reg. sbi0dbr load the data of 1st to (n 2)th. end of interrupt intsbi0 interrupt ((n 1) th receive data) 76543210 sbi0cr1 x x x 0 0 x x x not generate acknowledge signal reg. sbi0dbr load the data of (n 1)th end of interrupt intsbi0 interrupt (nth receive data) 76543210 sbi0cr1 0 0 1 0 0 x x x generate the clock for 1bit transmit reg. sbi0dbr receive the data of nth. end of interrupt intsbi0 interrupt (after receiving data) the process of generating stop condition finish the transmit of data end of interrupt note: x: don?t care d7 d6 2 9 3 4 5 6 7 8 1 d5 d4 d2 d3 d1 d0 1 scl pin sda pin intsbi interrupt request "0"  read sbi0dbr "001"  read sbi0dbr output of master output of slave acknowledge si g sent to a transmi t
page 160 2007-10-10 tmp91fu62 example: in case matching slave address in slave receive mode, direction bit is "1". intsbi0 interrupt if trx = 0 then shift to other process if al = 1 then shift to other process if aas = 0 then shift to other process 76543210 sbi0cr1 x x x 1 x x x x set the bit number of transmit. sbi0dbr x x x x x x x x set the data of transmit. note: x: don?t care table 8-1 operation in the slave mode conditions process 1 110 the tmp91fu62 loses arbitration when transmitting a slave address and receives a slave address for which the value of the direction bit sent from another master is ?1?. set the number of bits a word in and write the transmitted data to sbi0dbr. 0 10 in slave receiver mode, the tmp91fu62 receives a slave address for which the value of the direction bit sent from the master is ?1?. 00 in slave transmitter mode, a single word of data is transmitted. check the setting. if is set to ?1?, set to ?1? since the receiver win no request the data which follows. then, clear to ?0? to release the bus. if is cleared to ?0?, set to the number of bits in a word and write the transmitted data to sbi0dbr since the receiver requests next data. 0 1 11 / 0 the tmp91fu62 loses arbitration when transmitting a slave address and receives a slave address or general call for which the value of the direction bit sent from another master is ?0?. read the sbi0dbr for setting the to ?1? (reading dummy data) or set the to ?1?. 00 the tmp91fu62 loses arbitration when transmitting a slave address or data and terminates word data transfer. 0 11 / 0 in slave receiver mode, the tmp91fu62 receives a slave address or general call for which the value of the direction bit sent from the master is ?0?. 01 / 0 in slave receiver mode, the tmp91fu62 terminates receiving word data. set to the number of bits in a word and read the received data from sbi0dbr.
page 161 2007-10-10 tmp91fu62 8.3.4.4 stop condition generation when sbi0sr = ?1?, the sequence for generating a stop condition is started by writing ?1? to sbi0cr2 and ?0? to sbi0cr2. do not modify the contents of sbi0cr2 until a stop condition has been generated on the bus. when the bus?s scl line has been pulled low by another device, the tmp91fu62 generates a stop condition when the other device has released the scl line and sda pin rising. figure 8-13 stop condition generation (single master) figure 8-14 condition g eneration (multi master) 76543210 sbi0cr2 1 1 0 1 1 0 0 0 generate stop condition. internal scl 1  "1"  "0"  "1"  sda pin (read) stop condition scl pin internal scl "1"  "1"  "0"  "1"  sda pin (read) stop condition the case of pulled low by another device
page 162 2007-10-10 tmp91fu62 8.3.4.5 restart restart is used during data transfer between a master device and a slave to change the data transfer direction. the following description explains how to restart when the tmp91fu62 is in master mode. clear sbi0cr2 to ?0? and set sbi0 cr2 to ?1? to release the bus. the sda line remains high and the scl pin is released. since a stop condition has not been generated on the bus, other devices assume the bus to be in busy state. and confirm scl pin, that scl pin is released and become bus-free state by sbi0sr = ?0? or signal level ?1? of scl pin by sensing its port (chang e to input mode). check the until it becomes ?1? to check that the scl line on a bus is not pulled down to the low level by other devices. after con- firming that the bus remains in a free state, genera te a start condition using the procedure described in 8.3.4.2. in order to satisfy the setup time requirem ents when restarting, take at least 4.7 s of waiting time by software from the time of restarting to confirm that th e bus is free until the time to generate the start con- dition. figure 8-15 timing diagram for tmp91fu62 restart note: don't write "0", when "0" condition. (cannot be restarted) 76543210 sbi0cr2 00011000 release the bus if sbi0sr 0 check if scl pin is released. then if sbi0sr 1 check if scl pin of other device is "l" level. then 4.7us wait sbi0cr1 0 0 0 1 0 x x x set acknowledgement mode. sbi0dbr x x x x x x x x set the slave address and direction bit. sbi0cr2 11111000 generate start condition. note: x: don?t care "0"  "0"  "0"  "1"  "1"  "1"  "1"  "1"  9 internal scl scl pin sda pin start condition 4.7 s (min)
page 163 2007-10-10 tmp91fu62 9. 10-bit ad converter (adc) the tmp91fu62 have a 10-bit successive approximation ty pe ad converter. 9.1 configuration the circuit configuration of the 10-bit ad converter is shown in figure 9-1 . it consists of control register adccr1 and adccr2, converted value register adcdrh and adcdrl, a da converter, a sample-hold circuit, a compar ator, and a successive comparison circuit. note: before using ad converter, set appropriate value to i/o port register combining a analog input port. for details, see the sec- tion on "i/o ports". figure 9-1 10-bit ad converter 9.2 register configuration the ad converter consists of the following four registers: 1. ad converter control register 1 (adccr1) this register selects the analog channels and operation mode (single or repeat) in which to perform ad conversion and controls the ad converter as it starts operating. 2. ad converter control register 2 (adccr2) this register selects the ad conversion time and controls the connection of the da converter (ladder resistor network) and monitors the operating status of the ad converter. 3. ad converted value register (adcdrh, adcdrl) this register used to store the digital value after being converted by the ad converter. #0 #0   #0 #0 #%- 5#+0 #+0'0 #&4 5   #8%%  #855       # $      1 2 ; '0    5   #&%%4  4  4 4    # /& #&%%4 #&%&4.  #&%&4*   ' 1 % ( # & $ ( +06#&     45'.  analog input multiplexer da converter sample hold circuit reference voltage analog comparator shift clock control circuit ad conversion result register 1, 2 ad converter control register 1, 2 successive approximate circuit 5gngevqt
page 164 2007-10-10 tmp91fu62 note 1: select analog input channel during ad converter stops (adccr2 = ?0?). note 2: when the analog input channel is all use dis abling, the adccr1 should be set to ?0?. note 3: during conversion, do not perform port output instruction to maintain a precision for all of the pins because analog input port use as general input port. and for port near to anal og input, do not input intense signaling of change. note 4: the adccr1 is automatically cleared to ?0? after starting conversion. note 5: do not set adccr1 newly again during ad conv ersion. before setting adccr1 newly again, check adcdr2 to see that the conversion is completed or wait until the interrupt signal (intadc) is generated (e.g., interrupt handling routine). note 6: starting of stop mode, slow mode, and the idle1 mode initializes the ad control register 1 (adccr1) except for sain. moreover, in the case of the idle2 mode, it controls by the bit of adccr2. therefore, to use ad converter again, set the adccr1 newly after returning to normal mode. note 1: starting of stop mode, slow mode, and the idle1 mode in itializes the ad control register 2 (adccr2) except for ack and i2ad. moreover, in the case of the idle2 mode, it controls by the bit of adccr2. therefore, to use ad con- verter again, set the adccr2 newly after returning to norm al mode. therefore, the ad conversion result should be read to adcdrl more first than adcdrh. note 2: the adccr2 is cleared to ?0? when reading the adcdrh. note 3: the adccr2 is set to ?1? when ad conversi on starts, and cleared to ?0? when ad conversion finished. ad converter control register 1 76543210 adccr1 (02b0h) bit symbol adrs amd ainen sain read/write r/w a f t e r r e s e t00000000 function ad conver- sion start 0: - 1: ad con- version start ad operating mode 00: ad operation disable 01: single mode 10: reserved 11: repeat mode analog input control 0:disable 1:enable analog input channel select 0000: an0 0001: an1 0010: an2 0011: an3 0100: an4 0101: an5 0110: an6 0111: an7 1000: an8 1001: an9 1010: an10 1011: an11 1100: an12 1101: an13 1110: an14 1111: an15 ad converter control register 2 ( read-modify-write instructions are prohibited.) 76543210 adccr2 (02b1h) bit symbol eocf adbf rsel i2ad ack read/write r r/w a f t e r r e s e t00001100 function ad conver- sion end flag 0:before or during con- version 1: conver- sion com- pleted ad conver- sion busy flag 0: during stop of ad conversion 1: during ad conversion storing of an ad conver- sion result 0: 10bit mode 1: 8bit mode idle2 con- trol 0:stop 1:operation ad conversion time select see" table 9-1 ack setting and conversion time "
page 165 2007-10-10 tmp91fu62 note 1: setting for ?-? in the above table are inhibited. fc: high fr equency oscillation clock [hz] note 2: set conversion time setting should be kept mo re than the following time by analog reference voltage. note: at the time of 10-bit storing mode, if the bit 7 to 2 of adcdrh is read, ?0? will be read. table 9-1 ack setting and conversion time condition conversion time 20mhz 16mhz 10 mhz 8mhz 4 mhz ack 0xxx reserved 1000 reserved 1001 reserved 1010 78/fc ???? 19.5 s 1011 156/fc ?? 15.6 s 19.5 s 39.0 s 1100 312/fc 15.6 s 19.5 s 31.2 s 39.0 s 78.0 s 1101 624/fc 31.2 s 39.0 s 62.4 s 78.0 s156.0 s 1110 1248/fc 62.4 s 78.0 s 124.8 s 156.0 s ? 1111 reserved ? avcc = 4.5 to 5.5 v 15.6 us and more ad converted value register h (8-bit storing mode) 76543210 adcdrh (02b3h) bit symbol ad09 ad08 ad07 ad06 ad05 ad04 ad03 ad02 read/write r a f t e r r e s e t00000000 ad converted value register h (10-bit storing mode) 76543210 adcdrh (02b3h) bit symbol ?????? ad09 ad08 read/write r after reset00000000 ad converted value register l 76543210 adcdrl (02b2h) bit symbol ad07 ad06 ad05 ad04 ad03 ad02 ad01 ad00 read/write r a f t e r r e s e t00000000
page 166 2007-10-10 tmp91fu62 9.3 function 9.3.1 single mode after setting adccr1 to ?01? (single mode), set adccr1 to ?1?. ad conversion of the voltage at the analog input pin specifi ed by adccr1 is thereby started. after completion of the ad conversion, the conversion result is stored in ad converted value registers (adcdrh, adcdrl) and at the same time adccr2 is set to 1, the ad conversion finished inter- rupt (intadc) is generated. adccr1 is automatically cleared after ad c onversion has started. do not set adccr1 newly again (restart) during ad conversion. before setting adccr1 newly again, check adccr2 to see that the convers ion is completed or wait until th e interrupt signal (intadc) is gen- erated (e.g., interrupt handling routine). figure 9-2 single mode #&%&4zuvcvwu #&%%4'1%( +06#&%kpvgttwrvtgswguv #&%%4#&$( #&%%4#&45 #&%&4* #&%&4. conversion result read conversion result read conversion result read conversion result read indeterminate 1st conversion result 2nd conversion result ad conversion start ad conversion start eocf cleared by reading conversion result
page 167 2007-10-10 tmp91fu62 9.3.2 repeat mode ad conversion of the voltage at the analog input pin specified by adccr1 is performed repeat- edly. in this mode, ad conversion is star ted by setting adccr1 to ?1? after setting adccr1 to ?11? (repeat mode). after completion of the ad conversion, the conversion result is stored in ad converted value registers (adcdrl, adcdrh) and at the same time adccr2 is set to 1, the ad conversion finished inter- rupt (intadc) is generated. in repeat mode, each time one ad conversion is complete d, the next ad conversion is started. to stop ad conversion, set adccr1 to ?00? (disable mode) by writing 0s. the ad convert operation is stopped immediately. the converted valu e at this time is not stored in the ad converted value register. figure 9-3 repeat mode 9.3.3 register setting 1. set up the ad converter control re gister 1 (adccr1) as follows: ? choose the channel to ad convert using ad input channel select (sain). ? specify analog input enable fo r analog input control (ainds). ? specify amd for the ad converter control operation mode (ssingle or repeat mode). 2. set up the ad converter control re gister 2 (adccr2) as follows: set the ad conversion time using ad conversion time (ack). for details on how to set the con- version time, refer to table 9-1 and ad converter control register 2. 3. after setting up (1) and (2) above, set ad conversion st art (adrs) of ad converter control register 1 (adccr1) to ?1?. if software start mode has been selected, ad conversi on starts immediately. 4. after an elapse of the specified ad conversion time, the ad converted value is stored in ad con- verted value register (adcdrh and adcdrl) and the ad conversion finished flag (eocf) of ad converter control register 2 (adccr2) is set to ?1?, upon which time ad conversion interrupt intadc is generated. 5. eocf is cleared to ?0? by a read of the conversion re sult. however, if reconv erted before a register read, although eocf is cl eared the previous conversi on result is retained until the next conversion is completed.  #/&  '1%(   #&45   +06#&     #&%&4z        #/&  conversion operation ad conversion start 1st conversion result 2nd conversion result 3rd conversion result indeterminate 1st conversion result 3rd conversion result conversion result read ad convert operation suspended. conversion result is not stored. when not performing conversion result read-out, eocf is not cleared and a conversion result is not stored.
page 168 2007-10-10 tmp91fu62 9.4 idle1/stop/slow mo des during ad conversion when standby mode (idle1,stop or slow mode) is entered forcibly during ad conversion, the ad convert operation is suspended and the ad converter is initialized (adccr1 and adccr2 are initia lized to initial value). also, the conversion result is indeterminate. (conversion results up to the previous operation are cleared, so be sure to read the conversion results before entering standby mode (idle1,stop or slow mode).) when restored from standby mode (idle1,stop or slow m ode), ad conversion is not automatical ly restarted, so it is necessary to restart ad conversion. note that since the analog reference voltage is automati cally disconnected, there is no possi- bility of current flowing into the analog reference voltage. moreover, in the case of the idle2 mode, it controls by the bit of adccr2. example :after selecting the conversion time 19.5 s at 16 mhz and the analog input channel ain3 pin, perform ad con- version once. after checking eocf, read the converted value, store the lower 2 bits in address 0009eh nd store the upper 8 bits in address 0009fh in ram. the operation mode is single mode. ld (adccr1) , 00110011b ; select ain3 ld (adccr2) , 00001100b ;select conversion time(312/fc) and operation mode set (adccr1) . 7 ; adrs = 1(ad conversion start) sloop : test (adccr2) . 7 ; eocf= 1 ? jrs t, sloop ld a , (adcdrl) ; read result data ld (9eh) , a ld a , (adcdrh) ; read result data ld (9fh), a
page 169 2007-10-10 tmp91fu62 9.5 analog input voltage and ad conversion result the analog input voltage is corresponded to the 10-bit digital value converted by the ad as shown in figure 9-4 . figure 9-4 analog input voltage and ad conversion result (typ.) 10 01 h 02 h 03 h 3fd h 3fe h 3ff h 2 3 1021 1022 1023 1024 1024 ? 9 #8%% #855 analog input voltage a d conversion result
page 170 2007-10-10 tmp91fu62 9.6 precautions about ad converter 9.6.1 analog input pin voltage range make sure the analog input pins (an0 to an15) are used at voltages within avcc to avss. if any voltage outside this range is applied to one of the analog input pins, the converted value on that pin becomes uncertain. the other analog input pins also are affected by that. 9.6.2 analog input shared pins the analog input pins (an0 to an15) are shared with input/output ports. when using any of the analog inputs to execute ad convers ion, do not execute in put/output instructions for all other ports. this is necessary to prevent the accuracy of ad conversi on from degrading. not only these analog input shared pins, some other pins may also be affected by noise arising from input/o utput to and from adjacent pins. 9.6.3 noise countermeasure the internal equivalent circuit of the analog input pins is shown in figure 9-5 . the higher the output imped- ance of the analog input source, more easily they are su sceptible to noise. therefor e, make sure the output impedance of the signal source in your design is 5k or less. toshiba also reco mmends attaching a capacitor external to the chip. figure 9-5 analog inpu t equivalent circuit and example of i nput pin processing  ani 4m
6[r m
/cz %r(
6[r pqvgkvq da converter analog comparator internal resistance internal capacitance permissible signal source impedance
page 171 2007-10-10 tmp91fu62 10. program patch logic the tmp91fu62 has a program patch logic, which enables the user to fix the program code in the on-chip rom without generating a new mask. patch program must be re ad into on-chip ram from external memory during the startup routine. up to six two-byte sequences, or banks (twelve bytes in total) can be replaced with patch code. more significant code correction can be performed by replacing program code with single-byte instruction code which generates a software interrupt (swi) to make a branch to a specified location in the on-chip ram area. the program patch logic only compares addresses in the on-chip rom area; it cannot fix the program code in the on-chip peripheral, on-chip ram and external rom areas. each of six banks is independently programmable, and f unctionally equivalent. in the following sections, any ref- erences to bank0 also apply to other banks. 10.1 block diagram figure 10-1 program patch logic diagram %27 #fftguudwu
$cpm #fftguueqorctgtgikuvgtu
41/%/2vq41/%/2 41/4&
$cpm #fftguuuwduvkvwvkqp tgikuvgtu
41/57$.* &cvcdwu 41/ #fftguueqorctgdnqem 1wvrwveqpvtqndnqem /cvej ukipcn 41/4& 1wvrwv gpcdng
$cpm #fftguueqorctgtgikuvgtu
41/%/2vq41/%/2
$cpm #fftguueqorctgtgikuvgtu
41/%/2vq41/%/2
$cpm #fftguueqorctgtgikuvgtu
41/%/2vq41/%/2
$cpm #fftguueqorctgtgikuvgtu
41/%/2vq41/%/2
$cpm #fftguueqorctgtgikuvgtu
41/%/2vq41/%/2
$cpm #fftguuuwduvkvwvkqp tgikuvgtu
41/57$.*
$cpm #fftguuuwduvkvwvkqp tgikuvgtu
41/57$.*
$cpm #fftguuuwduvkvwvkqp tgikuvgtu
41/57$.*
$cpm #fftguuuwduvkvwvkqp tgikuvgtu
41/57$.*
$cpm #fftguuuwduvkvwvkqp tgikuvgtu
41/57$.*
page 172 2007-10-10 tmp91fu62 10.2 sfr descriptions the program patch logic consists of six banks (0 to 5). e ach bank is provided with th ree bytes of address compare registers (romcmpx0 to romcmpx2) and two bytes of address substitution regi sters (romsubxl and rom- subxh). note 1: the romcmp00/01/02, and romsub0l/0h regist ers do not support read-modify-write operation. note 2: bit0 of the address compare register 0 is read as undefined. bank0 address compare register 0 76543210 romcmp00 (0400h) rmw instructions are prohib- ited. bit symbol romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? read/write w ? a f t e r r e s e t0000000 ? function target rom address (lower 7 bits) ? bank0 address compare register 1 76543210 romcmp01 (0401h) rmw instructions are prohib- ited. bit symbol romc15 romc14 romc13 ro mc12 romc11 romc10 romc09 romc08 read/write w a f t e r r e s e t00000000 function target rom address (middle 8 bits) bank0 address compare register 2 76543210 romcmp02 (0402h) rmw instructions are prohib- ited. bit symbol romc23 romc22 romc21 ro mc20 romc19 romc18 romc17 romc16 read/write w a f t e r r e s e t00000000 function target rom address (upper 8 bits) bank0 data substitution register l 76543210 romsub0l (0404h) rmw instructions are prohib- ited. bit symbol roms07 roms06 roms05 ro ms04 roms03 roms02 roms01 roms00 read/write w after reset00000000 function patch code (lower 8 bits) bank0 data substitution register h 76543210 romsub0h (0405h) rmw instructions are prohib- ited. bit symbol roms15 roms14 roms13 ro ms12 roms11 roms10 roms09 roms08 read/write w a f t e r r e s e t00000000 function patch code (upper 8 bits)
page 173 2007-10-10 tmp91fu62 note 1: the romcmp10/11/12, and romsub1l/1h registers do not support read-modify-write operation. note 2: bit0 of the address compare register 0 is read as undefined. bank1 address compare register 0 76543210 romcmp10 (0408h) rmw instructions are prohib- ited. bit symbol romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? read/write w ? a f t e r r e s e t0000000 ? function target rom address (lower 7 bits) ? bank1 address compare register 1 76543210 romcmp11 (0409h) rmw instructions are prohib- ited. bit symbol romc15 romc14 romc13 ro mc12 romc11 romc10 romc09 romc08 read/write w after reset00000000 function target rom address (middle 8 bits) bank1 address compare register 2 76543210 romcmp12 (040ah) rmw instructions are prohib- ited. bit symbol romc23 romc22 romc21 ro mc20 romc19 romc18 romc17 romc16 read/write w a f t e r r e s e t00000000 function target rom address (upper 8 bits) bank1 data substitution register l 76543210 romsub1l (040ch) rmw instructions are prohib- ited. bit symbol roms07 roms06 roms05 ro ms04 roms03 roms02 roms01 roms00 read/write w a f t e r r e s e t00000000 function patch code (lower 8 bits) bank1 data substitution register h 76543210 romsub1h (040dh) rmw instructions are prohib- ited. bit symbol roms15 roms14 roms13 ro ms12 roms11 roms10 roms09 roms08 read/write w a f t e r r e s e t00000000 function patch code (upper 8 bits)
page 174 2007-10-10 tmp91fu62 note 1: the romcmp20/21/22, and romsub2l/2h regist ers do not support read-modify-write operation. note 2: bit0 of the address compare register 0 is read as undefined. bank2 address compare register 0 76543210 romcmp20 (0410h) rmw instructions are prohib- ited. bit symbol romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? read/write w ? a f t e r r e s e t0000000 ? function target rom address (lower 7 bits) ? bank2 address compare register 1 76543210 romcmp21 (0411h) rmw instructions are prohib- ited. bit symbol romc15 romc14 romc13 ro mc12 romc11 romc10 romc09 romc08 read/write w a f t e r r e s e t00000000 function target rom address (middle 8 bits) bank2 address compare register 2 76543210 romcmp22 (0412h) rmw instructions are prohib- ited. bit symbol romc23 romc22 romc21 ro mc20 romc19 romc18 romc17 romc16 read/write w a f t e r r e s e t00000000 function target rom address (upper 8 bits) bank2 data substitution register l 76543210 romsub2l (0414h) rmw instructions are prohib- ited. bit symbol roms07 roms06 roms05 ro ms04 roms03 roms02 roms01 roms00 read/write w a f t e r r e s e t00000000 function patch code (lower 8 bits) bank2 data substitution register h 76543210 romsub2h (0415h) rmw instructions are prohib- ited. bit symbol roms15 roms14 roms13 ro ms12 roms11 roms10 roms09 roms08 read/write w a f t e r r e s e t00000000 function patch code (upper 8 bits)
page 175 2007-10-10 tmp91fu62 note 1: the romcmp30/31/32, and romsub3l/3h regist ers do not support read-modify-write operation. note 2: bit0 of the address compare register 0 is read as undefined. bank3 address compare register 0 76543210 romcmp30 (0418h) rmw instructions are prohib- ited. bit symbol romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? read/write w ? a f t e r r e s e t0000000 ? function target rom address (lower 7 bits) ? bank3 address compare register 1 76543210 romcmp31 (0419h) rmw instructions are prohib- ited. bit symbol romc15 romc14 romc13 ro mc12 romc11 romc10 romc09 romc08 read/write w a f t e r r e s e t00000000 function target rom address (middle 8 bits) bank3 address compare register 2 76543210 romcmp32 (041ah) rmw instructions are prohib- ited. bit symbol romc23 romc22 romc21 ro mc20 romc19 romc18 romc17 romc16 read/write w a f t e r r e s e t00000000 function target rom address (upper 8 bits) bank3 data substitution register l 76543210 romsub3l (041ch) rmw instructions are prohib- ited. bit symbol roms07 roms06 roms05 ro ms04 roms03 roms02 roms01 roms00 read/write w a f t e r r e s e t00000000 function patch code (lower 8 bits) bank3 data substitution register h 76543210 romsub3h (041dh) rmw instructions are prohib- ited. bit symbol roms15 roms14 roms13 ro ms12 roms11 roms10 roms09 roms08 read/write w a f t e r r e s e t00000000 function patch code (upper 8 bits)
page 176 2007-10-10 tmp91fu62 note 1: the romcmp40/41/42, and romsub4l/4h regist ers do not support read-modify-write operation. note 2: bit0 of the address compare register 0 is read as undefined. bank4 address compare register 0 76543210 romcmp40 (0420h) rmw instructions are prohib- ited. bit symbol romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? read/write w ? a f t e r r e s e t0000000 ? function target rom address (lower 7 bits) ? bank4 address compare register 1 76543210 romcmp41 (0421h) rmw instructions are prohib- ited. bit symbol romc15 romc14 romc13 ro mc12 romc11 romc10 romc09 romc08 read/write w a f t e r r e s e t00000000 function target rom address (middle 8 bits) bank4 address compare register 2 76543210 romcmp42 (0422h) rmw instructions are prohib- ited. bit symbol romc23 romc22 romc21 ro mc20 romc19 romc18 romc17 romc16 read/write w a f t e r r e s e t00000000 function target rom address (upper 8 bits) bank4 data substitution register l 76543210 romsub4l (0424h) rmw instructions are prohib- ited. bit symbol roms07 roms06 roms05 ro ms04 roms03 roms02 roms01 roms00 read/write w a f t e r r e s e t00000000 function patch code (lower 8 bits) bank4 data substitution register h 76543210 romsub4h (0425h) rmw instructions are prohib- ited. bit symbol roms15 roms14 roms13 ro ms12 roms11 roms10 roms09 roms08 read/write w a f t e r r e s e t00000000 function patch code (upper 8 bits)
page 177 2007-10-10 tmp91fu62 note 1: the romcmp50/51/52, and romsub5l/5h regist ers do not support read-modify-write operation. note 2: bit0 of the address compare register 0 is read as undefined. bank5 address compare register 0 76543210 romcmp50 (0428h) rmw instructions are prohib- ited. bit symbol romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? read/write w ? a f t e r r e s e t0000000 ? function target rom address (lower 7 bits) ? bank5 address compare register 1 76543210 romcmp51 (0429h) rmw instructions are prohib- ited. bit symbol romc15 romc14 romc13 ro mc12 romc11 romc10 romc09 romc08 read/write w a f t e r r e s e t00000000 function target rom address (middle 8 bits) bank5 address compare register 2 76543210 romcmp52 (042ah) rmw instructions are prohib- ited. bit symbol romc23 romc22 romc21 ro mc20 romc19 romc18 romc17 romc16 read/write w a f t e r r e s e t00000000 function target rom address (upper 8 bits) bank5 data substitution register l 76543210 romsub5l (042ch) rmw instructions are prohib- ited. bit symbol roms07 roms06 roms05 ro ms04 roms03 roms02 roms01 roms00 read/write w a f t e r r e s e t00000000 function patch code (lower 8 bits) bank5 data substitution register h 76543210 romsub5h (042dh) rmw instructions are prohib- ited. bit symbol roms15 roms14 roms13 ro ms12 roms11 roms10 roms09 roms08 read/write w a f t e r r e s e t00000000 function patch code (upper 8 bits)
page 178 2007-10-10 tmp91fu62 10.3 operation 10.3.1 replacing data two consecutive bytes of data can be replaced for each bank. a two-byte sequence to be replaced must start at an even address. if only a sing le byte at an even or odd address n eed be replaced, set the current masked rom data in the other byte. correction procedure: load the address compare registers (romcmp00 to romcmp02) with the target address where rom data need be replaced. store 2-byte patch code in the romsub0l and romsub0h registers. when the cpu address matches the value stored in the romcmp00 to romcmp02 registers, the program patch logic disables rd output to the masked rom and drives out the code stored in the romsub0l and romsub0h to the internal bus. the cpu thus fetches the patch code. the following shows some examples: figure 10-2 example pa tch code implementation a. replacing 00h at address ff1230h with aah 76543210 romcmp00 0 0 1 1 0 0 0 0 stores 30 in address compare register 0 for bank0. romcmp01 0 0 0 1 0 0 1 0 stores 12 in address compare register 1 for bank0. romcmp02 1 1 1 1 1 1 1 1 stores ff in address compare register 2 for bank0. romsub0l 1 0 1 0 1 0 1 0 store aa in address substitution register low for bank0. romsub0h 0 0 0 1 0 0 0 1 store 11 in address substitution register high for bank0. 1pejkr rgtkrjgtcn  1pejkr4#/ 'zvgtpcnctgc 00h 11h 8gevqtvcdng ff1230h ff1231h replace with aah replace with 11h (same as current value). ffffffh c fe8000h 001000h 000000h 1pejkr41/
page 179 2007-10-10 tmp91fu62 figure 10-3 example pa tch code implementation figure 10-4 example pa tch code implementation b. replacing 33h at address ff1233h with bbh 76543210 romcmp00 0 0 1 1 0 0 1 0 stores 32 in address compare register 0 for bank0. romcmp01 0 0 0 1 0 0 1 0 stores 12 in address compare register 1 for bank0. romcmp02 1 1 1 1 1 1 1 1 stores ff in address compare register 2 for bank0. romsub0l 0 0 1 0 0 0 1 0 store 22 in address substitution register low for bank0. romsub0h 1 0 1 1 1 0 1 1 store bb in address substitution register high for bank0. c. replacing 44h at address ff1234h with cch and 55h at address ff1235h with ddh 76543210 romcmp00 0 0 1 1 0 1 0 0 stores 34 in address compare register 0 for bank0. romcmp01 0 0 0 1 0 0 1 0 stores 12 in address compare register 1 for bank0. romcmp02 1 1 1 1 1 1 1 1 stores ff in address compare register 2 for bank0. romsub0l 1 1 0 0 1 1 0 0 store cc in address substitution register low for bank0. romsub0h 1 1 0 1 1 1 0 1 store dd in address substitution register high for bank0. ff1232h ff1233h ffffffh d fe8000h 001000h 000000h 1pejkr rgtkrjgtcn  1pejkr4#/ 'zvgtpcnctgc 00h 11h 8gevqtvcdng 1pejkr41/ replace with 22h (same as current value). replace with bbh ff1234h ff1235h ffffffh e fe8000h 001000h 000000h 1pejkr rgtkrjgtcn  1pejkr4#/ 'zvgtpcnctgc 00h 11h 8gevqtvcdng 1pejkr41/ replace with cch replace with ddh
page 180 2007-10-10 tmp91fu62 figure 10-5 example pa tch code implementation d. replacing 77h at address ff1237h with eeh and 88h at address ff1238h with ffh (requiring two banks) 76543210 romcmp00 0 0 1 1 0 1 1 0 stores 36 in address compare register 0 for bank0. romcmp01 0 0 0 1 0 0 1 0 stores 12 in address compare register 1 for bank0. romcmp02 1 1 1 1 1 1 1 1 stores ff in address compare register 2 for bank0. romsub0l 0 1 1 0 0 1 1 0 store 66 in address substitution register low for bank0. romsub0h 1 1 1 0 1 1 1 0 store ee in address substitution register high for bank0. romcmp10 0 0 1 1 1 0 0 0 stores 38 in address compare register 0 for bank1. romcmp11 0 0 0 1 0 0 1 0 stores 12 in address compare register 1 for bank1. romcmp12 1 1 1 1 1 1 1 1 stores ff in address compare register 2 for bank1. romsub1l 1 1 1 1 1 1 1 1 store ff in address substitution register low for bank1. romsub1h 1 0 0 1 1 0 0 1 store 99 in address substitution register high for bank1. 66h 77h 88h 99h ff1236h ff1237h ff1238h ff1239h ffffffh f fe8000h 001000h 000000h 1pejkr rgtkrjgtcn  1pejkr4#/ 'zvgtpcnctgc 8gevqtvcdng 1pejkr41/ replace with 66h (same as current value). replace with eeh replace with ffh replace with 99h (same as current value).
page 181 2007-10-10 tmp91fu62 10.3.2 using an interrupt to cause a branch a wider range of program code can also be fixed using a software interrupt (swi). with a patch code loaded into on-chip ram, the progra m patch logic can be used to replace program code at a specified address with a single-byte swi instruction, which causes a branch to the patch program. note that this method can only be used if the original masked rom has been developed with on-chip ram addresses specified as swi vector addresses. correction procedure: load the address compare registers (romcmp00 to romcmp02) with the start address of the program code that is to be fixed. if it is an even address, store an swi instruction code (e.g., swi:f9h) in the rom- subl. if the start address is an odd address, store an swi instruction code in the romsubh and the current rom data at the preceding ev en address in the romsubl. when the cpu address matches the value stored in the romcmp00 to romcmp02 registers, the program patch logic disables rd output to the masked rom and drives out the swi instruction code to the internal bus. upon fetching the swi code, the cpu makes a branch to the internal ram area to ex ecute the preloaded code. at the end of the patch program executed from the in ternal ram, the cpu directly rewrites the saved pc value so that it points to the address follow ing the patch code, and then executes a reti. the following shows an example: example: fixing a program within the range from ff5000h to ff507fh before developing the original masked rom, set the swi1 vector reference address to 001500h (on- chip ram area). use the startup routine to load the patch code to on-chip ram (001500h to 0015efh). store the start address (ff5000h) of the rom area to be fixed in the romcmp00 to romcmp02. store the swi1 instruction code (f9h) in the romsub0l and the current data at ff5001h (aah) in the romsub0h. when the cpu address matches the value stored in romcmp00 to romcmp02, the program patch logic replaces the rom-based code at ff5000h with f9h. the cpu then executes the swi1 instruction, which causes a branch to 001500h in the on-chip ram area. after executing the patch program the cpu finally rewrites the saved pc value to ff5080h and executes a reti.
page 182 2007-10-10 tmp91fu62 figure 10-6 exampl e rom correction 1pejkr rgtkrjgtcn  1pejkr4#/ 'zvgtpcnctgc 1pejkr41/ 55h aah sw1 xgevqt (((* ((* replace the start address with f9h (swi1 instruction code). replace with aah (same as current value). &ghgevkxg ctgc ('* * * ((* ((* ((((* :* ((((* ((((* 8gevqtvcdng 001500h 2cvej rtqitco * n n n n * '(* 2tqitcodqf[ n n n n 4gytkvguvcem reti * '(* 4gvwtphtqo+06 $tcpejecwugfd[59 
page 183 2007-10-10 tmp91fu62 11. watchdog timer (runaway detection timer) the tmp91fu62 features a watchdog timer for detecting runaway. the watchdog timer (wdt) is used to return the cpu to normal state when it detects that the cpu has started to malfunction (runaway) due to causes such as noise. when the watchdog timer detects a malfunction, it gene rates a non-maskable interrupt intwd to notify the cpu. connecting the watchdog timer output to the reset pin internally forces a reset.(the level of external reset pin is not changed) 11.1 configuration figure 11-1 is a block diagram of he watchdog timer (wdt). figure 11-1 block diagram of watchdog timer note: it needs to care designing the total machine set, bec ause watchdog timer can?t operate completely by external noise. binary counter (22 stages) intwd interrupt reguest wdmod wdmod wdmod internal reset internal reset write 4eh write b1h q r s selector reset 2 15 wdt control register wdcr f sys (f fph /2) 2 17 2 19 2 21 reset reset control internal data bus
page 184 2007-10-10 tmp91fu62 11.2 operation the watchdog timer generates an intwd interrupt when the detection time set in the wdmod has elapsed. the watchdog timer must be cleared ?0? by software before an intwd interrupt will be generated. if the cpu malfunctions (e.g., if runaway occu rs) due to causes such as noise, but does not execute the instruction used to clear the binary counter, the binary co unter will overflow and an intwd interrupt will be generated. the cpu will detect malfunction (runaway) due to the intwd interrupt and in this case it is possible to return to the cpu to nor- mal operation by means of an anti-malfunction program. the watchdog timer works immediately after reset. the watchdog timer does not operate in idle1 or stop mode. when the device is in idle2 mode, the operation of wdt depends on the wdmod setting. ensure that wdmod is set before the device enters idle2 mode. the watchdog timer consists of a 22-stage bina ry counter which uses the system clock (f sys ) as the input clock. the binary counter can output f sys /2 15 , f sys /2 17 , f sys /2 19 and f sys /2 21 . figure 11-2 normal mode the runaway is detected when an overflow occurs, and the watchdog timer can reset this device. in this case, the reset time will be between 22 and 29 states (51.2 s at f osch = 20 mhz) as shown in figure 11-3. after a reset, the f sys clock (1 cycle = 1 state) is f fph /2, where f fph is generated by dividing the high-speed oscillator clock (f osch ) by sixteen through the clock gear function. figure 11-3 reset mode n overflow 0 wdt counter wdt clear (software) wdt interrupt write clear code n overflow wdt counter internal reset wdt interrupt 22 to 29 states  (26.1 to 34.4 s at f osch = 27 mhz, f fph = 1.7 mhz)
page 185 2007-10-10 tmp91fu62 11.3 control registers the watchdog timer wdt is controlled by two control registers wdmod and wdcr. 11.3.1 watchdog timer mode register (wdmod) a. setting the detection time for the watchdog timer in this 2-bit register is used for setting the watch dog timer interrupt time used when detecting run- away. after reset, this register is initialized to wdmod = ?00?(2 15 / f sys [s]). b. watchdog timer enable/disab le control register after reset, wdmod is initialized to ?1?, enabling the watchdog timer. to disable the watchdog timer, it is necessary to set this bit to ?0? and to write the disable code (b1h) to the watchdog timer control register wdcr. this makes it difficult for the watchdog timer to be disabled by runaway. however, it is possible to return the watchdog timer from the disabled state to the enabled state merely by setting to ?1?. c. watchdog timer out reset connection this register is used to connect the output of the watchdog timer with the internal reset. since wdmod is initialized to ?0? on reset, a reset by the watchdog timer will not be per- formed. 11.3.2 watchdog timer c ontrol register (wdcr) this register is used to disable and clear the binary counter for the watchdog timer. ? disable control the watchdog timer can be disabled by clearin g wdmod to ?0? and then writing the disable code (b1h) to the wdcr register. ? enable control set wdmod to ?1?. ? watchdog timer clear control to clear the binary counter and cause counting to resume, write the clear code (4 eh) to the wdcr register. wdmod 0 ? ? x x ? ? 0 clear wdmod to ?0?. wdcr 1 0 1 1 0 0 0 1 write the disable code (b1h). wdcr 01001110 write the clear code (4eh).
page 186 2007-10-10 tmp91fu62 watchdog timer mode register 76543210 wdmod (0300h) bit symbol wdte wdtp1 wdtp0 ? ? i2wdt rescr ? read/write r/w r/w ? ? r/w r/w a f t e r r e s e t100??000 function wdt control 1: enable select detecting time 00: 2 15 /f sys 01: 2 17 /f sys 10: 2 19 /f sys 11: 2 21 /f sys idle2 control reset control always write ?0?. watchdog timer out control rescr 0? 1 connect wdt out to a internal reset idle2 control i2wdt 0stop 1 operation watchdog timer detection time @fc = 20 mhz, fs = 32.768 khz syscr1 system clock selection syscr1 gear value watchdog timer detection time wdmod 00 01 10 11 1(fs) xxx 2.0 s 8.0 s 32.0 s 128.0 s 0(fc) 000 (fc) 3.28 ms 13.11 ms 52.43 ms 209.72 ms 001 (fc/2) 6.55 ms 26.21 ms 104.86 ms 419.43 ms 010(fc/4) 13.11 ms 52.43 ms 209.72 ms 838.86 ms 011 (fc/8) 26.21 ms 104.86 ms 419.43 ms 1677.72 ms 100 (fc/16) 52.43 ms 209.72 ms 838.86 ms 3355.44 ms watchdog timer enable/disable control wdte 0 disabled 1 enabled watchdog timer control register 76543210 wdcr (0301h) rmw instructions are prohib- ited. bit symbol - read/write w after reset - function b1h: wdt disable code 4eh: wdt clear code disable/clear wdt b1h disable code 4eh clear code others don?t care
page 187 2007-10-10 tmp91fu62 12. special timer for clock the tmp91fu62 includes a timer that is used for a clock operation. an interrupt (intrtc) can be generated each 0.0625 [s] or 0.125 [s] or 0.25 [s] or 0.50 [s] by using a low fre- quency clock of 32.768 khz. a clock function can be easily used. in addition, intrtc can return from each standby mode except stop mode. a special timer for clock can operate in all mode s in which a low-frequency oscillation is operated. the special timer for clock is contro lled by the special timer for clock control register (rtccr) as shown in. 12.1 configuration figure 12-1 blo ck diagram for special timer for clock special timer for clock control register 76543210 rtccr (0310h) bit symbol ????? rtcsel1 rtcsel0 rtcrun read/write r/w ???? r/w r/w after reset 0 ???? 000 function always write ?0?. ???? 00: 2 14 /fs 01: 2 13 /fs 10: 2 12 /fs 11: 2 11 /fs 0: stop & clear 1: count counting operation 0 stop & clear 1 count interrupt generation cycle (fs = 32.768 khz) 00 0.50 s 11 0.25 s 10 0.125 s 11 0.0625 s interrupt request intrtc fs (32.768 khz) run/ clear 2 11 rtccr rtccr 2 12 2 13 2 14 14-stage binary counter selector
page 188 2007-10-10 tmp91fu62 13. flash memory the tmp91fu62 incorporates flash me mory that can be electrically eras ed and programmed using a single 5v power supply. the flash memory is programmed and erased using jedec-standard commands. after a program or erase com- mand is input, the corresponding operation is automatically performed internally. erase operations can be performed by the entire chip (chip erase) or on a sector basis (sector erase). the configuration and oper ations of the flash memory are described below. 13.1 features 13.2 block diagram figure 13-1 block diagram of flash memory unit power supply voltage for program/erase operations sector size - vcc = 4.75 to 5.25 v - 8kbytes 12 (t opr = -10 to 40 c, fc = 4 to 20mhz) mode control configuration - jede c-standard commands - 48k 16 bits (96 k bytes) programming method functions - on-board programming - single-word programming - parallel programmer - chip erase security - sector erase - write protection - data polling / toggle bit - read protection +pvgtpcncfftguudwu 41/ eqpvtqnngt  oqfg eqpvtqn  oqfg ugvvkpirkp %qpvtqn  &cvc (ncujogoqt[ %qnwopfgeqfgt5gpugcor  &cvcncvej #fftguuncvej 'tcugugevqtfgeqfgt %qpvtqn ektewkv
kpenwfkpi cwvqocvke ugswgpeg eqpvtqn ektewkv  %qoocpf tgikuvgt           (ncujogoqt[egnnu    -$     4qyfgeqfgt  #fftguu +pvgtpcnfcvcdwu +pvgtpcneqpvtqndwu
page 189 2007-10-10 tmp91fu62 13.3 operation modes 13.3.1 overview the following three types of operation modes are availa ble to control program/erase operations on the flash memory. of the modes listed in table 13-1, the internal flash memory can be pr ogrammed in user boot mode, single boot mode and programmer mode. the mode in which the flash memory can be programmed/erased while mounted on the user board is defined as the on-board programming mode. of the modes listed above, single boot mode and user boot mode are classified as on-board programming modes. single bo ot mode supports toshiba's proprietary programming/ erase method using serial i/o. user boot mode (withi n single chip mode) allows the flash memory to be pro- grammed/erased by a user-specified method. programmer mode is provided with a read protect function which prohibits reading of rom data. by enabling the read protect function upon completion of programming, the user can protect rom data from being read by third parties. table 13-1 description of operation modes operation mode name description single chip mode after reset release, the device starts up from the internal flash memory. single chip mode is further divided into two m odes: ?normal mode? is a mode in which user application programs are executed, and ?user boot mode? is used to program the flash memory on-board. the means of switching between these two modes can be set by the user as desired. for exam- ple, it can be set so that port 00 = '1' selects normal mode and port 00 = '0' selects user boot mode. the user must include a routine to handle mode switching in a user application program. normal mode in this mode, the device starts up from a user application program. user boot mode in this mode, the flash memory can be programmed by a user-specified method. single boot mode after reset release, the device starts up from the internal boot rom (mask rom). the boot rom includes an algorithm which allows a pr ogram for programming/erasing the flash memory on-board via a serial port to be transferred to the device's internal ram. the transferred pro- gram is then executed in the internal ram so that the flash memory can be programmed/erased by receiving data from an external host and issuing program/erase commands. programmer mode this mode enables the internal flash memory to be programmed/erased using a general-pur- pose programmer. for programmers that can be us ed, please contact your local toshiba sales representative.
page 190 2007-10-10 tmp91fu62 the operation mode single chip mode, single boot m ode or programmer mode is determined during reset by externally setting the input levels on the am0, am1 and boot (emu0) pins. except in programmer mode which is entered with reset held at ?0?, the cpu will start operating in the selected mode after the reset state is released. once the operati on mode has been set, make sure that the input levels on the mode setting pins are not changed during operation.table 13-2 shows how to set each operation mode, and figure 13-2 shows a mode transition diagram. note: numbers in ( ) correspond to the operation mode pin settings shown in table 13-2. figure 13-2 mode transition diagram 13.3.2 reset operation to reset the device, hold the reset input at ?0? for at least 10 system clocks while the power supply volt- age is within the rated operating voltage range and the internal high-frequency oscillator is oscillating stably. for details, refer to ?reset of cpu?. table 13-2 operation mode pin settings operation mode input pins reset am1 am0 (1) single chip mode (normal or user boot mode) rising edge 11 (2) single boot mode 0 1 (3) programmer mode 0 1 0 1pdqctfrtqitcookpi  oqfg  4'5'6  4'5'6 
 

   5ykvejkpiogvjqf vqdgugvd[wugt  5kpingejkroqfg  4gugvuvcvg 
qt
  9  4'5'6  0qtocnoqfg  7ugt$qqv oqfg  5kping$qqv oqfg  2tqitcoogt oqfg
page 191 2007-10-10 tmp91fu62 13.3.3 memory map for each operation mode in this product, the memory map varies with operation mode. the memory map and sector address ranges for each operation mode are shown below. figure 13-3 memory map for each operation mode   * *  ((((((*    4gugtxgf  * * *  ('*  ((((*  ((((((*  +pvgtpcn+1 +pvgtpcn 4#/ -$    +pvgtpcn (ncuj41/ -$  
+pvgttwrvxgevqt$   (((*  * * * *   ((((*  ((((((*  *

m&?   ]+?  (ncuj41/ +pvgtpcn+1      +pvgtpcn$qqv41/  -$   
+pvgttwrvxgevqt$  +pvgtpcn (ncuj41/ -$ +pvgtpcn (ncuj41/ -$ +pvgtpcn 4#/ -$ 5k pi n g %jk roq f g 5k pi n g $ qqvoq f g 2tqitcookpioqfg external memory (access prohibited) external memory (access prohibited) external memory (access prohibited)
page 192 2007-10-10 tmp91fu62 table 13-3 sector address ranges for each operation mode single chip mode single boot mode sector-0 fe8000h to fe9fffh 10000h to 11fffh sector-1 fea000h to febfffh 12000h to 13fffh sector-2 fec000h to fedfffh 14000h to 15fffh sector-3 fee000h to feffffh 16000h to 17fffh sector-4 ff0000h to ff1fffh 18000h to 19fffh sector-5 ff2000h to ff3fffh 1a000h to 1bfffh sector-6 ff4000h to ff5fffh 1c000h to 1dfffh sector-7 ff6000h to ff7fffh 1e000h to 1ffffh sector-8 ff8000h to ff9fffh 20000h to 21fffh sector-9 ffa000h to ffbfffh 22000h to 23fffh sector-10 ffc000h to ffdfffh 24000h to 25fffh sector-11 ffe000h to ffffffh 26000h to 27fffh
page 193 2007-10-10 tmp91fu62 13.4 single boot mode in single boot mode, the internal boot rom (mask rom) is activated to transfer a program/erase routine (user- created boot program) from an external source into the inte rnal ram. this program/erase routine is then used to pro- gram/erase the flash memory. in this mode, the internal boot rom is mapped into an area containing the interrupt vector table, in which the boot rom program is executed. the flash memory is mapped into an address space differ- ent from the one into which the boot rom is mapped (see figure 13-3). the device's sio (sio1) and the contro ller are connected to transfer the pr ogram/erase routine from the controller to the device's internal ram. this pr ogram/erase routine is then executed to program/erase the flash memory. the program/erase routine is executed by sending commands and write data from the controller. the communications protocol between the device and the controller is describe d later in this manual. before the program/erase routine can be transferred to the ram, user passwor d verification is performed to ensure the security of user rom data. if the password is not verified co rrectly, the ram transfer operation cannot be performed. in single boot mode, disable interrupts and use the interrupt request fl ags to check for an interrupt request. note: do not change to another operation mode in the program/erase routine.
page 194 2007-10-10 tmp91fu62 13.4.1 using the program/e rase algorithm in the internal boot rom (step-1)environment setup since the program/erase routine and write data are transferred via si o (sio1), connect the device's sio (sio1) and the controller on the board. the user must prepare the program/erase routine (a) on the con- troller. (step-2) starting up the internal boot rom release the reset with the relevant input pins set for entering single boot mode. when the internal boot rom starts up, the program/erase rout ine (a) is transferred from the cont roller to the internal ram via sio according to the communications proced ure for single boot mode. before th is can be carried out, the password entered by the user is verified against the password writt en in the user application program. (if the flash mem- ory has been erased, 12 bytes of ? 0xff? are used as the password.) 
 6/2 (7 (ncujogoqt[  4#/     1nfwugtcrrnkecvkqp rtqitco
qtgtcugfuvcvg 
+1  $qqv41/  5+1
%qpvtqnngt 0gywugt crrnkecvkqp rtqitco  
c2tqitcogtcugtqwvkpg  
 6/2 (7 
  
+1    4'5'6 %qpfkvkqphqt gpvgtkpi5kping $qqvoqfg        4#/       5+1 (ncujogoqt[ 1nfwugtcrrnkecvkqp rtqitco
qtgtcugfuvcvg $qqv41/ %qpvtqnngt 0gywugt crrnkecvkqp rtqitco
c2tqitcogtcugtqwvkpg
page 195 2007-10-10 tmp91fu62 (step-3) copying the progra m/erase routine to the ram after password verification is completed, the boot rom copies the program/erase routine (a) from the con- troller to the ram using serial communications. the pr ogram/erase routine must be stored within the ram address range of 001000h to 001dffh. (step-4) executing the progra m/erase routine in the ram control jumps to the program/erase routine (a) in the ram. if necessary, the old user application program is erased (sector erase or chip erase). note 1: the boot rom is provided with an erase command, which enables the entire chip to be erased from the controller without using the program/erase routine. note 2: if it is necessary to erase data on a sector basis, incorporate the necessary code in the program/erase rou- tine. 
 6/2 (7   4#/      
 
+1       5+1
c2tqitcogtcugtqwvkpg  %qpvtqnngt 0gywugt crrnkecvkqp rtqitco
c2tqitcogtcugtqwvkpg (ncujogoqt[ 1nfwugtcrrnkecvkqp rtqitco
qtgtcugfuvcvg $qqv41/ 
 6/2 (7    4#/  
  
+1       5+1
c2tqitcogtcugtqwvkp g  'tcugf (ncujogoqt[ $qqv41/ %qpvtqnngt 0gywugt crrnkecvkqp rtqitco
c2tqitcogtcugtqwvkpg
page 196 2007-10-10 tmp91fu62 (step-5) copying the new user application program the program/erase routine (a) loads the new user application program from the controller into the erased area of the flash memory. in the example below, the new user application program is transferred under the same communications con- ditions as those used for transferring the program/erase routine. however, after the program/erase routine has been transferred, this routine can be used to change th e transfer settings (data bus an d transfer source). config- ure the board hardware and program/erase routine as desired. (step-6) executing the new user application program after the programming operation has been completed, tu rn off the power to the board and remove the cable connecting the device and the controll er. then, turn on the power again and start up the device in single chip mode to execute the new user application program. 
 6/2 (7   4#/    0gywugtcrrnkecvkqp rtqitco    
 
+1      5+1  %qpvtqnngt 0gywugt crrnkecvkqp rtqitco
c2tqitcogtcugtqwvkpg
c2tqitcogtcugtqwvkpg (ncujogoqt[ $qqv41/ 
 6/2 (7 
     4'5'6  %qpfkvkqphqt gpvgtkpi5kping %jkroqfg
0qtocnoqfg      4#/        5+1  0gywugtcrrnkecvkqp rtqitco (ncujogoqt[ $qqv41/ %qpvtqnngt
page 197 2007-10-10 tmp91fu62 13.4.2 connection examples for single boot mode in single boot mode the flash memory is programme d by serial transfer. therefore, on-board programming is performed by connecting the device's sio (sio1) a nd the controller (programming tool) and sending com- mands from the controller to the device. figure 13-4 shows an example of connection between the target board and a programming controller. figure 13-5 shows an example of connection between the target board and an rs232c board. figure 13-4 example of connection with an external c ontroller in single boot mode &8%% 8%% 45% 41/ /qfgeqpvtqn 2tqitco eqpvtqnngt 8%%  8%% 4gi 1p$qctf2tqitcookpi%qpvtqnngt 4'5'6 /%7 6ctigvdqctf qrgtcvkqp 4'5'6 4#/ 6/2(7 #/ 2% 855 &855 2 2 6:&
2 4:&
2 4:& 6:& 2 2 2qygt uwrrn[ $qqv oqfg uykvejkpi ektewkv 6ctigv$qctf /qfgeqpvtqn
page 198 2007-10-10 tmp91fu62 figure 13-5 example of connection with an rs232c b oard in single boot mode 6ctigv$qctf  &8%% 8%% 45% 8%%  8%% 2qygt uwrrn[ 45% $qctf 4'5'6 #/ 4'5'6 $qqv oqfg uykvejkpi ektewkv #/ 6/2(7 #/ 2% 855 &855 6:&
2 4:&
2 4:& 6:& 855
page 199 2007-10-10 tmp91fu62 13.4.3 mode setting to perform on-board programming, the device must be started up in single boot mode by setting the input pins as shown below. am0 = 1 am1 = 0 reset = 0 1 set the am0 and am1 pins as shown above with the reset pin held at ?0?. then, setting the reset pin to ?1? will start up the devi ce in single boot mode. 13.4.4 memory maps figure 13-6 shows a comparison of the memory map for normal mode (in single chip mode) and the mem- ory map for single boot mode. in single boot mode, the flash memory is mapped to addresses 10000h to 27fffh (physical addresses) and the boot rom (mask rom) is mapped to addresses fff000h to ffffffh. figure 13-6 comparison of memory maps 5kping%jkroqfg 5kping$qqvoqfg 000000h 001000h 002000h fe 8000h ffff00h ffffffh fff000h 000000h 001000h 010000h 028000h ffff00h ffffffh 002000 h (
m&? ) ]+? flash rom internal i/o internal ram 4kb internal flash rom 96 kb internal i/o internal ram 4kb internal boot rom 4kb internal flash rom 96 kb (interrupt vector 256b) (interrupt vector 256b) external memory (access prohibited) external memory (access prohibited) external memory (access prohibited)
page 200 2007-10-10 tmp91fu62 13.4.5 interface specifications the sio communications format in single boot mode is shown below. the device supports the uart (asynchronous communications) serial operation mode. to perform on-board programming, the same communi cations format must also be set on the programming controller's side. note: unused pins are in the initial state after reset release. uart (asynchronous) communications - communications channel : sio channel 1(for the pins be used, see table 13-4 ) - serial transfer mode : uart (asynchronous communications) mode - data length : 8 bits - parity bit : none - stop bit : 1 bit - baud rate : see table 13-5 , table 13-6 table 13-4 pin connections pins uart power sup- ply pins dvcc dvss mode set- ting pins am1,am0 reset pin reset communi- cations pins txd1 rxd1 table 13-5 baud rate table sio transfer rate (bps) uart 115200 57600 38400 19200 9600
page 201 2007-10-10 tmp91fu62 reference frequency: the frequency of the high-speed oscillation circ uit that can be used in single boot mode. to program the flash memory using single boot mode, one of the reference frequencies must be selected as a high-speed clock. supported range: the range of clock frequencies that are detected as each reference frequency. it may not be possible to perform single boot operations at clock fr equencies outside of the supported range. note:to automatically detect the reference frequency (micro controller clock frequency), the transfer baud rate error of the flash memory programming controller and the oscillation frequency error must be within ?1.5 %, + 2% in total. table 13-6 correspondence betw een operating frequency and baud rate in single boot mode 115200 error (%) - - - - 0 - - - baud rate (bps) - - - - 115200 - - - 57600 error (%) - - - - 0 - 0 - baud rate (bps) - - - - 57600 - 57600 - 38400 error (%) - +1.73 - 0 0 - - +1.73 baud rate (bps) - 39063 - 38400 38400 - - 39063 19200 error (%) - +1.73 0 0 0 +0.16 0 +1.73 baud rate (bps) - 19531 19200 19200 19200 19231 19200 19531 9600 error (%) +0.16 +1.73 0 0 0 +0.16 0 +1.73 baud rate (bps) 9615 9766 9600 9600 9600 9615 9600 9766 reference baud rate (bps) supported range (mhz) 7 .87 to 8.14 9.69 to 10.02 10.90 to 11.28 12.11 to 12.53 14.53 to 15.04 15.74 to 16.29 18.16 to 18.80 19.37 to 20.05 reference frequency (mhz) 8 10 11.0592 12.288 14.7456 16 18.4320 20
page 202 2007-10-10 tmp91fu62 13.4.6 data transfer formats table 13-7 to table 13-12 show the operation command data and the data transfer format for each operation mode. table 13-7 operation command data operation command data operation mode 10h ram transfer 20h flash memory sum 30h product information read 40h flash memory chip erase 60h flash memory protect set
page 203 2007-10-10 tmp91fu62 table 13-8 transfer format of single boot program [ram transfer] transfer byte number transfer data from controller to device baud rate transfer data from device to controller boot rom 1st byte baud rate setting uart 86h desired baud rate #1 #1 for the desired baud rate setting, see table 13-6 . - 2nd byte - ack response to baud rate setting normal (baud rate ok) >uart 86h (if the desired baud rate cannot be set, operation is terminated.) 3rd byte operation command data (10h) - 4th byte - ack response to operation command #2 normal 10h error x1h protection applied #3 x6h communications error x8h #2 after sending an error response, the device waits for operation command data (3rd byte). #3 when read protection or write protection is applied, the device aborts the received operation command and waits for the next operation command data (3rd byte). 5th byte to 16th byte password data (12 bytes) (027ef4h to 027effh) - 17th byte checksum value for 5th to 16th bytes - 18th byte - ack response to checksum value #2 normal 10h error 11h communications error 18h 19th byte ram storage start address 31 to 24 #4 #4 the data to be transferred in the 19th to 25th bytes should be programmed within the ram address range of 001000h to 001dffh (3.5 kbytes). - 20th byte ram storage start address 23 to 16 #4 - 21th byte ram storage start address 15 to 8 #4 - 22th byte ram storage start address 7 to 0 #4 - 23th byte ram storage byte count 15 to 8 #4 - 24th byte ram storage byte count 7 to 0 #4 - 25th byte checksum value for 19th to 24th bytes #4 - 26th byte - ack response to checksum value #2 normal 10h error 11h communications error 18h 27th byte to (m)th byte ram storage data - (m+1)th byte checksum value for 27th to m'th bytes - (m+2)th byte - ack response to checksum value #2 normal 10h error 11h communications error 18h ram (m+3)th byte - jump to ram storage start address
page 204 2007-10-10 tmp91fu62 table 13-9 transfer format of single boot program [flash memory sum] transfer byte number transfer data from controller to device baud rate transfer data from device to controller boot rom 1st byte baud rate setting uart 86h desired baud rate #1 #1 for the desired baud rate setting, see table 13-6 . - 2nd byte - ack response to baud rate setting normal (baud rate ok) >uart 86h (if the desired baud rate cannot be set, operation is terminated.) 3rd byte operation command data (20h) - 4th byte - ack response to checksum value #2 normal 20h error x1h communications error x8h #2 after sending an error response, the device waits for operation command data (3rd byte). 5th byte - sum (upper) 6th byte - sum (lower) 7th byte - checksum value for 5th and 6th bytes 8th byte (wait for the next operation command data) -
page 205 2007-10-10 tmp91fu62 table 13-10 transfer format of single boot program [product information read](1/2) transfer byte number transfer data from controller to device baud rate transfer data from device to controller boot rom 1st byte baud rate setting uart 86h desired baud rate #1 - 2nd byte - ack response to baud rate setting normal (baud rate ok) >uart 86h (if the desired baud rate cannot be set, operation is terminated.) 3rd byte operation command data (30h) - 4th byte - ack response to operation command #2 normal 30h error x1h communications x8h 5th byte - flash memory data (address 027ef0h) 6th byte - flash memory data (address 027ef1h) 7th byte - flash memory data (address 027ef2h) 8th byte - flash memory data (address 027ef3h) 9th byte to 20th byte - part number (ascii code, 12 bytes) 'tmp91fu62_ _ _ ' (from 9th byte) 21th byte to 24th byte - password comparison start address (4 bytes) f4h, 7eh, 02h, 00h (from 21st byte) 25th byte to 28th byte - ram start address (4 bytes) 00h, 10h, 00h, 00h (from 25th byte) 29th byte to 32th byte - ram (user area) end address (4 bytes) ffh, 1dh, 00h, 00h (from 29th byte) 33th byte to 36th byte - ram end address (4 bytes) ffh, 1fh, 00h, 00h (from 33rd byte) 37th byte to 40th byte - dummy data (4 bytes) 00h,00h,00h,00h (from 37th byte) 41th byte to 44th byte - dummy data (4 bytes) 00h, 00h, 00h, 00h (from 41st byte) 45th byte to 46th byte - fuse information (2 bytes from 45th byte) read protection/write protection 1) applied/applied : 00h, 00h 2) not applied/applied : 01h, 00h 3) applied/not applied : 02h, 00h 4) not applied/not applied : 03h, 00h 47th byte to 50th byte - flash memory start address (4 bytes) 00h, 00h, 01h, 00h (from 47th byte) 51th byte to 54th byte - flash memory end address (4 bytes) ffh, 7fh, 02h, 00h (from 51st byte) 55th byte to 56th byte - number of sectors in flash memory (2 bytes) 0ch, 00h (from 55th byte) 57th byte to 60th byte - start address of flash memory sectors of the same size (4 bytes) 00h, 00h, 01h, 00h (from 57th byte)
page 206 2007-10-10 tmp91fu62 61th byte to 64th byte - size (in half words) of flash memory sectors of the same size (4 bytes) 00h, 10h, 00h, 00h (from 61st byte) 65th byte - number of flash memory sectors of the same size (1 byte) 0ch 66th byte - checksum value for 5th to 65th bytes 67th byte (wait for the next operation command data) - #1 for the desired baud rate setting, see table 13-6 . #2 after sending an error response, the device waits for operation command data (3rd byte). table 13-11 transfer format of single boot program [flash memory chip erase] transfer byte number transfer data from controller to device baud rate transfer data from device to controller boot rom 1st byte baud rate setting uart 86h desired baud rate #1 #1 for the desired baud rate setting, see table 13-6 . - 2nd byte - ack response to baud rate setting normal (baud rate ok) >uart 86h (if the desired baud rate cannot be set, operation is terminated.) 3rd byte operation command data (40h) - 4th byte - ack response to operation command #2 normal 40h error x1h communications x8h #2 after sending an error response, the device waits for operation command data (3rd byte). 5th byte erase enable command data (54h) - 6th byte - ack response to operation command #2 normal 54h error x1h communications x8h 7th byte - ack response to erase command normal 4fh error 4ch 8th byte - ack response normal 5dh error 60h 9th byte (wait for the next operation command data) - table 13-10 transfer format of single boot program [product information read](2/2) transfer byte number transfer data from controller to device baud rate transfer data from device to controller
page 207 2007-10-10 tmp91fu62 table 13-12 transfer format of single boot program [flash memory protect set] transfer byte number transfer data from controller to device baud rate transfer data from device to controller boot rom 1st byte baud rate setting uart 86h desired baud rate #1 #1 for the desired baud rate setting, see table 13-6 . - 2nd byte - ack response to baud rate setting normal (baud rate ok) >uart 86h (if the desired baud rate cannot be set, operation is terminated.) 3rd byte operation command data (60h) - 4th byte - ack response to operation command #2 normal 60h error x1h communications x8h #2 after sending an error response, the device waits for operation command data (3rd byte). 5th byte to 16th byte password data (12 bytes) (027ef4h to 027effh) - 17th byte checksum value for 5th to 16th bytes - 18th byte - ack response to checksum value #2 normal 60h error 61h communications 68h 19th byte - ack response to protect set command normal 6fh error 6ch 20th byte - ack response normal 31h error 34h 21th byte (wait for the next operation command data) -
page 208 2007-10-10 tmp91fu62 13.4.7 boot program when the device starts up in single boot mode, the boot program is activated. the following explains the commands that are used in the boot program to communicate w ith the controller when the device starts up in single boot mode. use this information for creating a controller for using single boot mode or for building a user boot environment. 1. ram transfer command in ram transfer, data is transferred from the controller and stored in the device's internal ram. when the transfer completes normally, the boot pr ogram will start running th e transferred user pro- gram. up to 3.5 kbytes of data can be transferre d as a user program. (this limit is implemented in the boot program to protect the st ack pointer area.) the user progra m starts executing from the ram storage start address. this ram transfer function enables a user-created program/erase routine to be executed, allowing the user to implement their ow n on-board programming method. to perform on-board programming with a user program, the flash memory command sequences (see section 13.6) must be used. after the ram transfer command has been completed, the entire internal ram area can be used. if read protection or write protection is applied on the device or a password error occurs, this com- mand will not be executed. 2. flash memory sum command this command calculates the sum of 96 kbytes of data in the flash memory and returns the result. there is no operation comm and available to the boot program for reading data from the entire area of the flash memory. instead, this flash memory su m command can be used. reading the sum value enables revision management of the application program. 3. product information read command this command returns the information about the device including its part number and memory details stored in the flash memory at addresse s 027ef0h to 027ef3h. this command can also be used for revision management of the application program. 4. flash memory chip erase command this command erases all the sector s in the flash memory. if read protection or write protection is applied on the device, all the sectors in the flash me mory are erased and the read protection or write protection is cleared. since this command is also used to restore the operation of the boot program when the password is forgotten, it does not include password verification. 5. flash memory protect set command this command sets both read pr otection and write protection on the device. however, if a pass- word error occurs, this comm and will not be executed. when read protection is set, the flash memory cannot be read in programmer mode. when write protection is set, the flash memory cannot be written in programmer mode.
page 209 2007-10-10 tmp91fu62 13.4.8 ram transfer command see table 13-8. 1. from the controller to the device the data in the 1st byte is used to determine the baud rate. the 1st byte is transferred with receive operation disabled (sc1mod0 = 0). (the baud rate is determined using an internal timer.) to communicate in uart mode send the value 86h from the controller to the target board using uart settings at the desired baud rate. if the serial operation mode is de termined as uart, the device checks to see whether or not the desired baud rate can be set. if the device determines that the desired baud rate cannot be set, operation is terminated and no communications can be established. 2. from the device to the controller the data in the 2nd byte is the ack response returned by the device for the serial operation mode setting data sent in the 1st byte. if the data in the 1st byte is found to signify uart and the desired baud rate can be set, the device returns 86h. baud rate determination the device determines whether or not the desired baud rate can be set. if it is found that the baud rate can be set, the boot program rewrites the br1cr and br1add values and returns 86h. if it is found that the desired baud rate cannot be set, operation is terminated and no data is returned. the controller sets a time-out time (5 seconds) after it has finished sending the 1st byte. if the contro ller does not receive the response (86h) normally w ithin the time-out time, it should be considered that the device is unable to communicate. receive operation is enabled (sc1mod0 = 1) before 86h is written to the transmission buffer. 3. from the controller to the device the data in the 3rd byte is op eration command data. in this case, the ram transfer command data (10h) is sent from the controller to the device. 4. from the device to the controller the data in the 4th byte is the ack response to the operation command data in the 3rd byte. first, the device checks to see if the received data in the 3rd byte contains any error. if a receive error is found, the device returns the ack response data fo r communications error (bit 3) x8h and waits for the next operation command data (3rd byte). the upper four bits of the ack response data are unde- fined (they are the upper four bits of the immediately preceding operation command data). next, if the data received in th e 3rd byte correspond s to one of the oper ation commands given in table 13-7, the device echoes back the received data (ack response for normal reception). in the case of the ram transfer command, if read or wr ite protection is not applied, 10h is echoed back and then execution branches to the ram transfer processing routine. if protection is applied, the device returns the corresponding ack response data (bit 2/1) x6h and waits for the next operation command data (3rd byte). the upper four bits of the ack response data are undefined. (they are the upper four bits of th e immediately preceding op eration command data.) after branching to the ram transf er processing routine, the device checks the data in the password area. for details, see " 13.4.15 password ". if the data in the 3rd byte does not correspond to any operation command, the device returns the ack response data for operation command error (b it0) x1h and waits for the next operation com- mand data (3rd byte). the upper four bits of the ack response data are undefined. (they are the upper four bits of th e immediately preceding op eration command data.)
page 210 2007-10-10 tmp91fu62 5. from the controller to the device the 5th to 16th bytes contain password data (12 bytes). the data in the 5th to 16th bytes is verified against the data at addresses 027ef4h to 027effh in the flash memory, respectively. 6. from the controller to the device the 17th byte contains checksum data. the checksum data sent by the controller is the two's complement of the lower 8-bit value obtained by summing the data in the 5th to 16th bytes by unsigned 8-bit addition (ignoring any overflow). for details on checksum, see " 13.4.17 how to calculate checksum ". 7. from the device to the controller the data in the 18th byte is the ack response data to the 5th to 17th bytes (ack response to the checksum value). the device first checks to see whet her the data received in the 5th to 17th bytes contains any error. if a receive error is found, the device return s the ack response data for commu- nications error (bit 3) 18h and waits for the next operation command data (3rd byte). the upper four bits of the ack response data are the upper four bits of the immediatel y preceding operation com- mand data, so the value of these bits is ?1?. next, the device checks the checksum data in the 17th byte. this check is made to see if the lower 8-bit value obtained by summing the data in the 5th to 17th bytes by unsigned 8-bit addition (ignoring any overflow) is 00h. if the value is not 00h, the device returns the ack response data for checksum error (bit 0) 11h and waits for the next operation command data (3rd byte). finally, the device examines the result of password verification. if all the data in the 5th to 16th bytes is not verified correctly, the device return s the ack response data for password error (bit 0) 11h and waits for the next operation command data (3rd byte). if no error is found in all the above checks, the device returns the ack response data for normal reception 10 h. 8. from the controller to the device the data in the 19th to 22nd bytes indicates the ra m start address for storing block transfer data. the 19th byte corresponds to address bits 31 to 24, the 20th byte to address bits 23 to 16, the 21st byte to address bits 15 to 8, and the 22nd byte to address bits 7 to 0. 9. from the controller to the device the data in the 23rd and 24th byt es indicates the number of bytes to be transferred. the 23rd byte corresponds to bits 15 to 8 of the transfer byte co unt and the 24th byte corresponds to bits 7 to 0. 10. from the controller to the device the data in the 25th byte is checksum data. th e checksum data sent by the controller is the two's complement of the lower 8-bit value obtained by summing the data in the 19th to 24th bytes by unsigned 8-bit addition (ignoring any overflow). for details on checksum, see " 13.4.17 how to calculate checksum ". note: the data in the 19th to 25th bytes should be placed within addresses 001000h to 001dffh (3.5kbytes) in the internal ram.
page 211 2007-10-10 tmp91fu62 11. from the device to the controller the data in the 26th byte is the ack response data to the data in the 19th to 25th bytes (ack response to the checksum value). the device first checks to see whether the data received in the 19th to 25th bytes contains any error. if a receive error is found, the device retu rns the ack response data for communications error (bit 3) 18h and waits for the next operation command (3rd byte). the upper four bits of the ack response data are the upper four bits of the immediately preceding operation command data, so the value of these bits is ?1?. next, the device checks the checksum data in the 25th byte. this check is made to see if the lower 8-bit value obtained by summing the data in the 19th to 25th bytes by unsigned 8-bit addition (ignoring any overflow) is 00h. if the value is not 00h, the device returns the ack response data for checksum error (bit 0) 11h and waits for the next operation command data (3rd byte). 12. from the controller to the device the data in the 27th to m'th bytes is the data to be stored in the ram. this data is written to the ram starting at the address specified in the 19th to 22nd bytes. the number of bytes to be written is specified in the 23rd and 24th bytes. 13. from the controller to the device the data in the (m+1)th byte is checksum data . the checksum data sent by the controller is the two's complement of the lower 8-bit value obtained by summing the data in the 27th to m'th bytes by unsigned 8-bit addition (ignoring any overflow). for details on checksum, see " 13.4.17 how to calculate checksum ". 14. from the device to the controller the data in the (m+2)th byte is the ack response data to the 27th to (m+1)th bytes (ack response to the checksum value). the device first checks to see whether the data in th e 27th to (m+1)th byte contains any error. if a receive error is found, the device returns the ack response data for communications error (bit 3) 18h and waits for the next operat ion command (3rd byte). the upper four bits of the ack response are the upper four bits of the immediately preceding operation comma nd data, so the value of these bits is ?1?. next, the device checks the checksum data in the (m +1)th byte. this check is made to see if the lower 8-bit value obtained by summing the data in the 27th to (m+1)th bytes by unsigned 8-bit addi- tion (ignoring any overflow) is 00h. if the valu e is not 00h, the device returns the ack response data for checksum error (bit 0) 11h and waits for the next operation command data (3rd byte). if no error is found in all the above checks, the device returns the ack response data for normal reception 10h. 15. from the device to the controller if the ack response data in the (m+2)th byte is 10h (normal reception), the boot program then jumps to the ram start address sp ecified in the 19th to 22nd bytes.
page 212 2007-10-10 tmp91fu62 13.4.9 flash memory sum command see table 13-9. 1. the data in the 1st and 2nd bytes is the same as in the case of th e ram transfer command. 2. from the controller to the device the data in the 3rd byte is operation comm and data. the flash memory sum command data (20h) is sent here. 3. from the device to the controller the data in the 4th byte is the ack response data to the operation command data in the 3rd byte. the device first checks to see if the data in the 3rd byte contains any erro r. if a receive error is found, the device returns the ack response data fo r communications error (bit 3) x8h and waits for the next operation command data (3rd byte). the upper four bits of the ack response data are unde- fined. (they are the upper four bits of the immediately pr eceding operation command data.) then, if the data in the 3rd byte corresponds to one of the operation command values given in table 13-7, the device echoes back the received data (ack respons e for normal reception). in this case, 20h is echoed back and execu tion then branches to the flas h memory sum processing routine. if the data in the 3rd byte does not correspond to any operation command, the device returns the ack response data for operation command error (b it 0) x1h and waits for the next operation com- mand data (3rd byte). the upper four bits of the ack response data are undefined. (they are the upper four bits of th e immediately preceding op eration command data.) 4. from the device to the controller the data in the 5th and 6th bytes is the upper and lower data of the sum value, respectively. for details on sum, see " 13.4.16 how to calculate sum ". 5. from the device to the controller the data in the 7th byte is checksum data. this is the two's complement of the lower 8-bit value obtained by summing the data in the 5th and 6th bytes by unsigned 8-bit addition (ignoring any overflow). 6. from the controller to the device the data in the 8th byte is the next operation command data.
page 213 2007-10-10 tmp91fu62 13.4.10product information read command see table 13-10. 1. the data in the 1st and 2nd bytes is the same as in the case of th e ram transfer command. 2. from the controller to the device the data in the 3rd byte is operation command data. the product inform ation read command data (30h) is sent here. 3. from the device to the controller the data in the 4th byte is the ack response data to the operation command data in the 3rd byte. the device first checks to see if the data in the 3rd byte contains any erro r. if a receive error is found, the device returns the ack response data fo r communications error (bit 3) x8h and waits for the next operation command data (3rd byte). the upper four bits of the ack response data are unde- fined. (they are the upper four bits of the immediately pr eceding operation command data.) then, if the data in the 3rd byte corresponds to one of the operation command values given in table 13-7, the device echoes back the received data (ack respons e for normal reception). in this case, 30h is returned and executi on then branches to the product information read processing rou- tine. if the data in the 3rd byte does not correspond to any operation command, the device returns the ack response data for operation command error (b it 0) x1h and waits for the next operation com- mand data (3rd byte). the upper four bits of the ack response data are undefined. (they are the upper four bits of th e immediately preceding op eration command data.) 4. from the device to the controller the data in the 5th to 8th bytes is the data stored at addresses 027ef0h to 027ef3h in the flash memory. by writing the id information of software at these addresses, the version of the software can be managed. (for example, 0002h can indi cate that the software is now in version 2.) 5. from the device to the controller the data in the 9th to 20th bytes denotes the pa rt number of the device. 'tmp91fu62_ _ _' is sent in ascii code starting from the 9th byte. note: an underscore ('_') indicates a space. 6. from the device to the controller the data in the 21st to 24th bytes is the password comparison start address. f4h, 7eh, 02h and 00h are sent starting from the 21st byte. 7. from the device to the controller the data in the 25th to 28th bytes is the ram star t address. 00h, 10h, 00h and 00h are sent start- ing from the 25th byte. 8. from the device to the controller the data in the 29th to 32nd bytes is the ram (user area) end address. ffh, 1dh, 00h and 00h are sent starting from the 29th byte. 9. from the device to the controller the data in the 33rd to 36th bytes is the ram en d address. ffh, 1fh, 00 h and 00h are sent start- ing from the 33rd byte. 10. from the device to the controller the data in the 37th to 44th bytes is dummy data. 11. from the device to the controller the data in the 45th and 46th bytes contains the protection status and sector division information of the flash memory. >bit 0 indicates the read protection status. 0: read protection is applied.
page 214 2007-10-10 tmp91fu62 1: read protection is not applied. >bit 1 indicates the write protection status. 0: write protection is applied. 1: write protection is not applied. >bit 2 indicates whether or not the flash memory is divided into sectors. 0: the flash memory is divided into sectors. 1: the flash memory is not divided into sectors. >bits 3 to 15 are sent as ?0?. 12. from the device to the controller the data in the 47th to 50th bytes is the flash memory start address. 00h, 00h, 01h and 00h are sent starting from the 47th byte. 13. from the device to the controller the data in the 51st to 54th bytes is the flash memory end address. ffh, 7fh, 02h and 00h are sent starting from the 51st byte. 14. from the device to the controller the data in the 55th and 56th bytes indicates the number of sectors in the flash memory. 0ch and 00h are sent starting from the 55th byte. 15. from the device to the controller the data in the 57th to 65th bytes contains sect or information of the flas h memory. sector informa- tion is comprised of the start address (starting from the flash memory start address), sector size and number of consecutive sectors of the same size. note that the sector size is represented in word units. the data in the 57th to 65th bytes indicates 8 kbytes of sectors (sec tor 0 to sector 11). for the data to be transferred, see table 13-10. 16. from the device to the controller the data in the 66th byte is checksum data. this is the two's complement of the lower 8-bit value obtained by summing the data in the 5th to 65th bytes by unsigned 8-bit addition (ignoring any overflow). 17. from the controller to the device the data in the 67th byte is the next operation command data.
page 215 2007-10-10 tmp91fu62 13.4.11flash memory chip erase command see table 13-11. 1. the data in the 1st and 2nd bytes is the same as in the case of th e ram transfer command. 2. from the controller to the device the data in the 3rd byte is operation command da ta. the flash memory chip erase command data (40h) is sent here. 3. from the device to the controller the data in the 4th byte is the ack response data to the operation command data in the 3rd byte. the device first checks to see if the data in the 3rd byte contains any erro r. if a receive error is found, the device returns the ack response data fo r communications error (bit 3) x8h and waits for the next operation command data (3rd byte). the upper four bits of the ack response data are unde- fined. (they are the upper four bits of the immediately preced ing operation command data.) then, if the data in the 3rd byte corresponds to one of the operation command values given in table 13-7, the device echoes back the received data (ack respons e for normal reception). in this case, 40h is echoed back. if the data in the 3rd byte does not correspond to any operation command, the device returns the ack response data for operation command error (bit 0) x1h and waits for the next operation command data (3rd byte). the uppe r four bits of the ack response data are unde- fined. (they are the upper four bits of the immediately pr eceding operation command data.) 4. from the controller to the device the data in the 5th byte is erase enable command data (54h). 5. from the device to the controller the data in the 6th byte is the ack response data to the erase enable command data in the 5th byte. the device first checks to see if the data in the 5t h byte contains any error. if a receive error is found, the device returns the ack response data fo r communications error (bit 3) x8h and waits for the next operation command data (3rd byte). the upper four bits of the ack response data are unde- fined (they are the upper four bits of th e immediately preceding operation command data.) then, if the data in the 5th byte corresponds to the erase enable command data, the device echoes back the received data (ack response for normal reception). in this case, 54h is echoed back and execution jumps to the flash memory chip erase processing routine. if the data in the 5th byte does not correspond to the erase enable command data , the device returns the ack response data for operation command error (bit 0) x1h and waits for the next operation command (3rd byte). the upper four bits of the ack respons e data are undefined. (they are the upper four bits of the immedi- ately preceding operat ion command data.) 6. from the device to the controller the data in the 7th byte indicates whether or not the erase operation has completed successfully. if the erase operation has completed successfully, the de vice returns the end code (4fh). if an erase error has occurred, the device re turns the error code (4ch). 7. from the device to the controller the data in the 8th byte is ack response data. if the erase operation ha s completed successfully, the device returns the ack response for erase comple tion (5dh). if an erase error has occurred, the device returns the ack response for erase error (60h). 8. from the controller to the device the data in the 9th byte is the next operation command data.
page 216 2007-10-10 tmp91fu62 13.4.12flash memory protect set command see table 13-12. 1. the data in the 1st and 2nd bytes is the same as in the case of th e ram transfer command. 2. from the controller to the device the data in the 3rd byte is operation command data. the flash memory protect set command data (60h) is sent here. 3. from the device to the controller the data in the 4th byte is the ack response data to the operation command data in the 3rd byte. the device first checks to see if the data in the 3rd byte contains any erro r. if a receive error is found, the device returns the ack response data fo r communications error (bit 3) x8h and waits for the next operation command data. the upper four bits of the ack response data are undefined. (they are the upper four bits of the im mediately preceding operation command data.) then, if the data in the 3rd byte corresponds to one of the operation command data values given in table 13-7, the device echoes back the received data (ack respons e for normal reception). in this case, 60h is echoed back and execu tion branches to the fl ash memory protect set processing routine. after branching to this routine, the data in the password area is checked. for details, see " 13.4.15 password ". if the data in the 3rd byte does not correspond to any operation command, the device returns the ack response data for operation command error (bit 0) x1h and waits for the next oper- ation command data (3rd byte). the upper four bits of the ack response data are undefined. (they are the upper four bits of the immediately precedin g operation command data.) 4. from the controller to the device the data in the 5th to 16th bytes is password data (12 bytes). the data in the 5th byte is verified against the data at address 027ef4h in the flash me mory and the data in the 6th byte against the data at address 027ef5h. in this manner, the received data is verified consecutively against the data at the specified address in the flash memory. the data in th e 16th byte is verified ag ainst the data at address 027effh in the flash memory. 5. from the controller to the device the data in the 17th byte is checksum data. th e checksum data sent by the controller is the two's complement of the lower 8-bit value obtained by summing the data in 5th to 16th bytes by unsigned 8-bit addition (ignoring any overflow). for details on checksum, see " 13.4.17 how to calculate checksum ". 6. from the device to the controller the data in the 18th byte is the ack response data to the data in the 5th to 17th bytes (ack response to the checksum value). the device first checks to see whether the data in the 5th to 17th bytes contains any error. if a receive error is found, the device returns the ack response data for communications error (bit 3) 68h and waits for the next operation command data (3rd byte). the upper four bits of the ack response data are the upper four bits of the immediately preceding operation command data, so the value of these bits is ?6?. then, the device checks the checksum data in the 17th byte. this check is made to see if the lower 8 bits of the value obtained by summing the data in the 5th to 17th bytes by unsigned 8-bit addition (ignoring any overflow) is 00h. if the value is not 00h, the device returns the ack response data for checksum error (bit 0) 61h and waits for the next operation command data (3rd byte). finally, the device examines the result of password verification. if all the data in the 5th to 16th bytes is not verified correctly, the device return s the ack response data for password error (bit 0) 61h and waits for the next operation command data (3rd byte). if no error is found in the ab ove checks, the device returns the ack response data for normal reception 60h.
page 217 2007-10-10 tmp91fu62 7. from the device to the controller the data in the 19th byte indicates whether or not the protect set opera tion has completed success- fully. if the operation has completed successfully, th e device returns the end code (6fh). if an error has occurred, the device retu rns the error code (6ch). 8. from the device to the controller the data in the 20th byte is ack response data. if the protect set operat ion has completed success- fully, the device returns the ack response data for normal completion (31h). if an error has occurred, the device returns the ack response data for error (34h). 9. from the device to the controller the data in the 21st byte is the next operation command data. 13.4.13ack response data the boot program notifies the controller of its processing status by sending various response data. table 13- 13 to table 13-18 show the ack respons e data returned for each type of received data. the upper four bits of ack response data are a direct refl ection of the upper four bits of th e immediately preceding operation com- mand data. bit 3 indicates a receive error and bit 0 indicates an operat ion command error, checksum error or password error. note: if the desired baud rate cannot be set, the device returns no data and terminates operation. note:the upper four bits are a direct reflection of the upper four bits of the immediately preceding operation com- mand data. table 13-13 ack response data to serial operation mode setting data transfer data meaning 86h the device can communicate in uart mode. (note) table 13-14 ack response data to operation command data transfer data meaning x8h (note) a receive error occurred in the operation command data. x6h (note) terminated receive operation due to protection setting. x1h (note) undefined operation command data was received normally. 10h received the ram transfer command. 20h received the flash memory sum command. 30h received the product information read command. 40h received the flash memory chip erase command. 60h received the flash memory protect set command. table 13-15 ack response data to checksum data for ram transfer command transfer data meaning 18h a receive error occurred. 11h a checksum error or password error occurred. 10h received the correct checksum value.
page 218 2007-10-10 tmp91fu62 note:these codes are returned for reconfirmation of communications. note:these codes are returned for reconfirmation of communications. 13.4.14determining serial operation mode to communicate in uart mode, the cont roller should transmit the data va lue 86h as the first byte at the desired baud rate. figure 13-7 shows the waveform of this operation. figure 13-7 data for determ ining serial operation mode the boot program receives the first byte (86h) after re set release not as serial communications data. instead, the boot program uses the first byte to determine the ba ud rate. the baud rate is determined by the output peri- ods of tab, tac and tad as shown in figure 13-7 using the procedure shown in figure 13-8. the cpu monitors the level of the receive pin. upon detecting a level change, the cpu captures the timer value to determine the baud rate. table 13-16 ack response data to flash memory chip erase operation transfer data meaning 54h received the erase enable command. 4fh completed erase operation. 4ch an erase error occurred. 5dh (note) reconfirmation of erase operation 60h (note) reconfirmation of erase error table 13-17 ack response data to checksum data for flash memory protect set command transfer data meaning 68h a receive error occurred. 61h a checksum or password error occurred. 60h received the correct checksum value. table 13-18 ack response data to flash memory protect set operation transfer data meaning 6fh completed the protect (read/write) set operation. 6ch a protect (read/write) set error occurred. 31h (note) reconfirmation of protect (read/write) set operation 34h (note) reconfirmation of protect (read/write) set error 7#46
 *   v#$  2qkpv#  2qkpv$ 2qkpv% 2qkpv& dkv dkv dkv  dkv dkv dkv dkv dkv 5vctv 5vqr  v# &  v# % 
page 219 2007-10-10 tmp91fu62 figure 13-8 flowchart for serial operation mode receive operation initialize 16-bit timer b0 ( t1 = 8/fc, clear counter) start the prescaler start counting up of 16-bit timer b0 point a stop operation (endless loop) receive pin changed from high to low? yes yes yes start receive pin changed from low to high? capture timer value (tab) by software receive pin changed from high to low? capture timer value (tac) by software yes receive pin changed from low to high? capture timer value (tad) by software stop 16-bit timer b0 tac tad? back up tad value end yes point b point c point d
page 220 2007-10-10 tmp91fu62 13.4.15password when the ram transfer command (1 0h) or the flash memory protect set command (60h) is received as operation command data, password verification is performe d. first, the device echoes back the operation com- mand data (10h to 60h) and checks the data (12 bytes) in the password area (addresses 027ef4h to 027effh). then, the device verifies the password data received in the 5th to 16th bytes against the data in the password area as shown in table 13-19. unless all the 12 bytes are verified co rrectly, a password error will occur. a password error will also occur if all the 12 bytes of password data contain the same value. only exception is when all the 12 bytes ar e ?ffh? and verified correctly and the reset vector area (addresses 027f00h to 027f02h) is all ?ffh?. in this case, a blank device will be assumed and no password error will occur. if a password error has occurred, the device returns th e ack response data for password error in the 18th byte. table 13-19 password verification table receive data data to be verified against 5th byte data at address 027ef4h 6th byte data at address 027ef5h 7th byte data at address 027ef6h 8th byte data at address 027ef7h 9th byte data at address 027ef8h 10th byte data at address 027ef9h 11th byte data at address 027efah 12th byte data at address 027efbh 13th byte data at address 027efch 14th byte data at address 027efdh 15th byte data at address 027efeh 16th byte data at address 027effh example of data that cannot be specified as a password for blank products (note) the password of a blank product must be all ?ffh? (ffh, ffh, ffh, ffh, ffh, ffh, ffh, ffh, ffh, ffh, ffh, ffh). note:a blank product is a product in which all the bytes in the password area (addresses 02fef4h to 02feffh) and the reset vector area (addresses 02ff00h to 02ff02h) are ?ffh?. for programmed products the same 12 consecutive bytes cannot be specified as a password. the table below shows password error examples. programmed product 1 2 3 4 5 6 7 8 9 10 11 12 note error example 1 ffh ffh ffh ffh ffh ffh ffh ffh ffh ffh ffh ffh all"ff" error example 2 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h 00h all"00" error example 3 5ah 5ah 5ah 5ah 5ah 5ah 5ah 5ah 5ah 5ah 5ah 5ah all"5a"
page 221 2007-10-10 tmp91fu62 13.4.16how to calculate sum sum is calculated by summing the values of all data read from the flash memory by unsigned 8-bit addition and is returned as a word (16-bit) value. the resulting sum value is sent to the controller in order of upper 8 bits and lower 8 bits. all the 96 kbytes of data in the flash memory are included in the calculation of sum. when the flash memory sum command is ex ecuted, sum is calculated in this way. 13.4.17how to calculate checksum checksum is calculated by taking the two's complement of the lower 8-bit value obtained by summing the values of received data by unsign ed 8-bit addition (ignoring any over flow). when the flash memory sum command or the product info rmation read command is executed, checksum is calculated in this way. the controller should also use this checksum calculation method for sending checksum values. example: calculating checksum for the flash memory sum command when the upper 8-bit data of sum is e5h and the lower 8-bit data is f6h, checksum is calculated as shown below. first, the upper 8 bits and lower 8 bits of the sum value are added by unsigned operation. e5h+f6h = 1dbh then, the two's complement of the lower 8 bits of this result is obtained as shown below. the resulting checksum value (25h) is sent to the controller. 0-dbh = 25h 13.5 user boot mode (in single chip mode) user boot mode, which is a sub mode of single chip mode, enables a user-created flash memory program/erase routine to be used. to do so, the operation mode of single chip mode must be changed from normal mode for exe- cuting a user application program to user boot mode for programming/erasing the flash memory. for example, the reset processing rou tine of a user application program may include a routine fo r selecting normal mode or user boot mode upon entering single chip mo de. any mode-selecting condition may be set using the device's i/o to suit the user system. to program/erase the flash memory in user boot mode, a program/erase routine must be incorporated in the user application program in advance. since the processor cannot read data from th e internal flash memory while it is being programmed or erased, the program/erase routine mu st be executed from the outside of the flash memory. while the flash memory is being programmed/erased in user boot mode, interrupts must be disabled. the pages that follow explain the procedure for progra mming the flash memory usi ng two example cases. in one case the program/erase routine is stored in the internal flash memory (1-a); in the other the program/erase routine is transferred from an ex ternal source (1-b).  #*  $*  %*  &*  9jgp57/kuecnewncvgfhtqovjghqwtfcvcgpvtkgu ujqypvqvjgnghvvjgtguwnvkucuhqnnqyu  #* $* %* &*'#*      57/wrrgtdkvu*    57/nqygtdkvu'#*   6jwuvjg57/xcnwgkuugpvvqvjgeqpvtqnngtkp qtfgtqh*cpf'#*
page 222 2007-10-10 tmp91fu62 13.5.1 (1-a) program/era se procedure example 1 when the program/erase routine is stored in the internal flash memory (step-1)environment setup first, the condition (e.g. pin status) for entering user boot mode must be set and the i/o bus for trans- ferring data must be determined. then, the device's peripheral circuitry must be designed and a corre- sponding program must be written. before mounting the device on the board, it is necessary to write the following four routines into one of the sectors in the flash memory. (a)mode select routine: selects normal mode or user boot mode. (b)program/erase routine: loads program/erase data from an external source and programs/erases the flash memory. (c)copy routine 1: copies routines (a) to (d) into the internal ram or external memory. (d)copy routine 2: copies routines (a) to (d) from the internal ram or external memory into the flash memory. note:the above (d) is a routine for reconstructing the progr am/erase routine on the flash memory. if the entire flash memory is always programmed and the program/erase routine is included in the new user application pro- gram, this copy routine is not needed. 
6/2(7  4#/  = ?    
     
+1     %qpvtqnngt 0gywugt crrnkecvkqp rtqitco (ncujogoqt[ 1nfwugtcrrnkecvkqp rtqitco  4gugvrtqeguukpitqwvkpg
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg 
page 223 2007-10-10 tmp91fu62 (step-2) entering user boot mode (using the reset processing) after reset release, the reset pro cessing program determines whether or not the device should enter user boot mode. if the condition for entering user boot mode is true, user boot mode is entered to program/ erase the flash memory. (step-3) copying the program/erase routine after the device has entered user boot mode, the copy routine 1 (c) copies the routines (a) to (d) into the internal ram or external memory (the rout ines are copied into the internal ram here.)   4#/  = ?   
    
+1       4'5'6 %qpfkvkqphqt gpvgtkpi7ugt $qqvoqfg
wugturgekhkgf     
6/2(7 (ncujogoqt[ 1nfwugtcrrnkecvkqp rtqitco  4gugvrtqeguukpitqwvkpg
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg  %qpvtqnngt 0gywugt crrnkecvkqp rtqitco      4#/  = ?    
  
+1        
6/2(7 (ncujogoqt[ 1nfwugtcrrnkecvkqp rtqitco  4gugvrtqeguukpitqwvkpg
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg 
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg  %qpvtqnngt 0gywugt crrnkecvkqp rtqitco
page 224 2007-10-10 tmp91fu62 (step-4) erasing the flash memory by the program/erase routine control jumps to the program/erase routine in the ram and the old user progr am area is erased (sector erase or chip erase). (in this case, the flash memory erase comm and is issued from the ram.) note: if data is erased on a sector basis and the routines (a) to (d) are left in the flash memory, only the program/ erase routine (b) need be copied into the ram. (step-5) restoring the user boot program in the flash memory the copy routine 2 (d) in the ram copies the routines (a) to (d) into the flash memory. note: if data is erased on a sector basis and the routines (a) to (d) are left in the flash memory, step 5 is not needed.   4#/ 
     
+1      'tcugf
6/2(7 %qpvtqnngt 0gywugt crrnkecvkqp rtqitco (ncujogoqt[
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg       4#/  = ?  
  
+1       
6/2(7 (ncujogoqt[  4gugvrtqeguukpitqwvkpg
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg 
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg  %qpvtqnngt 0gywugt crrnkecvkqp rtqitco
page 225 2007-10-10 tmp91fu62 (step-6) writing the new user application program to the flash memory the program/erase routine in the ra m is executed to load the new us er application program from the controller into the erased area of the flash memory. (step-7) executing the new user application program the reset input pin is driven low (?0?) to reset the device. the mode setting condition is set for nor- mal mode. after reset release, the device will st art executing the new us er application program.   4#/  = ?  
     
+1          
6/2(7 (ncujogoqt[ 1nfwugtcrrnkecvkqp rtqitco  4gugvrtqeguukpitqwvkpg
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg 
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg  %qpvtqnngt 0gywugt crrnkecvkqp rtqitco   4#/  = ?    
   
+1       4'5'6 %qpfkvkqphqt gpvgtkpi0qtocn oqfg  
6/2(7 (ncujogoqt[ 1nfwugtcrrnkecvkqp rtqitco  4gugvrtqeguukpitqwvkpg
f%qr[tqwvkpg 
e%qr[tqwvkpg
c/qfgugngevtqwvkpg
d2tqitcogtcugtqwvkpg  %qpvtqnngt
page 226 2007-10-10 tmp91fu62 13.5.2 (1-b) program/era se procedure example 2 in this example, only the boot program (minimum requirement) is stored in the flash memory and other nec- essary routines are supp lied from the controller. (step-1)environment setup first, the condition (e.g. pin status) for entering user boot mode must be set and the i/o bus for trans- ferring data must be determined. then, the device's peripheral circuitry must be designed and a corre- sponding program must be written. before mounting the device on the board, it is necessary to write the following two routines into one on the sectors in the flash memory. (a)mode select routine: selects normal mode or user boot mode. (b)transfer routine: loads the program/erase routin e from an ex ternal source. the following routines are pr epared on the controller. (c)program/erase routine: programs/erases the flash memory. (d)copy routine 1: copies routines (a) and (b) into th e internal ram or external memory. (e)copy routine 2: copies routines (a) and (b) from the internal ram or external memory into the flash memory. 
%qpvtqnngt  
+1  (ncujogoqt[  4#/  = 4gugvrtqeguukpitqwvkpg ?
c /qfgugngevtqwvkpg  1nfwugtcrrnkecvkqp  rtqitco  
d 6tcpuhgttqwvkpg    
e2tqitcogtcugtqwvkpg
f%qr[tqwvkpg 
g%qr[tqwvkpg  
6/2(7 0gywugtcrrnkecvkqp rtqitco
page 227 2007-10-10 tmp91fu62 (step-2) entering user boot mode (using the reset processing) the following explanation assumes that these routines are incorporated in the reset processing program. after reset release, the reset pro cessing program first determines whether or not the device should enter user boot mode. if the condition for entering user boot mode is true, user boot mode is entered to pro- gram/erase the flash memory. (step-3) copying the program/eras e routine to the internal ram after the device has entered user boot mode, the tran sfer routine (b) transfers the routines (c) to (e) from the controller to the internal ram (or external memory). (the routines are copied into the internal ram here.) 
 
+1    4'5'6 %qpfkvkqphqt gpvgtkpi7ugt $qqvoqfg
wugturgekhkgf      4#/  = ?
c    
d 6tcpuhgttqwvkpg      
6/2(7 (ncujogoqt[  4gugvrtqeguukpitqwvkpg /qfgugngevtqwvkpg 1nfwugtcrrnkecvkqp rtqitco %qpvtqnngt
e2tqitcogtcugtqwvkpg
f%qr[tqwvkpg
g%qr[tqwvkpg  0gywugtcrrnkecvkqp rtqitco 
  
+1   4#/  = ?
c /qfgugngevtqwvkpg     
e2tqitcogtcugtqwvkpg   
g%qr[tqwvkpg  
f%qr[tqwvkpg  
6/2(7 %qpvtqnngt
e2tqitcogtcugtqwvkpg
f%qr[tqwvkpg
g%qr[tqwvkpg  0gywugtcrrnkecvkqp rtqitco (ncujogoqt[  4gugvrtqeguukpitqwvkpg 1nfwugtcrrnkecvkqp rtqitco
d 6tcpuhgttqwvkpg
page 228 2007-10-10 tmp91fu62 (step-4) executing the copy ro utine 1 in the internal ram control jumps to the internal ram and the copy rout ine 1 (d) copies the routin es (a) and (b) into the internal ram. (step-5) erasing the flash memory by the program/erase routine the program/erase routine (c) eras es the old user program area. 
  
+1   4#/  = ?
c    
d      
g%qr[tqwvkpg  
f%qr[tqwvkpg
c/qfgugngevtqwvkpg 
d6tcpuhgttqwvkpg 
e2tqitcogtcugtqwvkpg 
6/2(7 (ncujogoqt[ /qfgugngevtqwvkpg 1nfwugtcrrnkecvkqp rtqitco 6tcpuhgttqwvkpg  4gugvrtqeguukpitqwvkpg %qpvtqnngt
e2tqitcogtcugtqwvkpg
f%qr[tqwvkpg
g%qr[tqwvkpg  0gywugtcrrnkecvkqp rtqitco 
  
+1   4#/            'tcugf 
6/2(7
g%qr[tqwvkpg 
f%qr[tqwvkpg
c/qfgugngevtqwvkpg
d6tcpuhgttqwvkpg 
e2tqitcogtcugtqwvkpg  (ncujogoqt[ %qpvtqnngt
e2tqitcogtcugtqwvkpg
f%qr[tqwvkpg
g%qr[tqwvkpg  0gywugtcrrnkecvkqp rtqitco
page 229 2007-10-10 tmp91fu62 (step-6) restoring the user boot program in the flash memory the copy routine (e) copies the ro utines (a) and (b) from the internal ram into the flash memory. (step-7) writing the new user application program to the flash memory the program/erase routine (c) in the ram is execute d to load the new user application program from the controller into the eras ed area of the flash memory. 
  
+1   4#/  = ?           
6/2(7
c
d
g%qr[tqwvkpg 
f%qr[tqwvkpg
c/qfgugngevtqwvkpg
d6tcpuhgttqwvkpg 
e2tqitcogtcugtqwvkpg  (ncujogoqt[ /qfgugngevtqwvkpg 6tcpuhgttqwvkpg  4gugvrtqeguukpitqwvkpg %qpvtqnngt
e2tqitcogtcugtqwvkpg
f%qr[tqwvkpg
g%qr[tqwvkpg  0gywugtcrrnkecvkqp rtqitco 
  
+1   4#/  = ?          
 
6/2(7 %qpvtqnngt
e2tqitcogtcugtqwvkpg
f%qr[tqwvkpg
g%qr[tqwvkpg  0gywugtcrrnkecvkqp rtqitco
c
d
g%qr[tqwvkpg 
f%qr[tqwvkpg
c/qfgugngevtqwvkpg
d6tcpuhgttqwvkpg 
e2tqitcogtcugtqwvkpg  (ncujogoqt[ /qfgugngevtqwvkpg 1nfwugtcrrnkecvkqp rtqitco 6tcpuhgttqwvkpg  4gugvrtqeguukpitqwvkpg
page 230 2007-10-10 tmp91fu62 (step-8) executing the new user application program the reset input pin is driven low (?0?) to reset the device. the mode setting condition is set for nor- mal mode. after reset release, the device will st art executing the new us er application program. 
  
+1    4'5'6 %qpfkvkqphqt gpvgtkpi0qtocn oqfg   4#/  = ?       
6/2(7
c
d (ncujogoqt[ /qfgugngevtqwvkpg 1nfwugtcrrnkecvkqp rtqitco 6tcpuhgttqwvkpg  4gugvrtqeguukpitqwvkpg %qpvtqnngt
page 231 2007-10-10 tmp91fu62 13.6 flash memory command sequences the operation of the flash memory is comprised of six commands, as shown in table 13-20. addresses specified in each command sequence must be in an area where the fl ash memory is mapped. for details, see table 13-3. note 1: pa = program word address, pd = program word data set the address and data to be programmed. even-numbered addresses should be specified here. note 2: sa = sector erase address, each sector erase range is selected by address a23 to a13. note 3: when apply read protect and write protect, be sure to program the data of 00h. note: d15 to d8 and d5 to d0 are ?don't care?. table 13-20 command sequences command 1st bus write cycle 2nd bus write cycle 3rd bus write cycle 4th bus write cycle 5th bus write cycle 6th bus write cycle sequence addr. data addr. data addr. data addr. data addr. data addr. data 1 single word program aaah aah 554h 55h aaah a0h pa (note1) pd (note1) 2 sector erase (8kb erase) aaah aah 554h 55h aaah 80h aaah aah 554h 55h sa (note2) 30h 3 chip erase (all erase) aaah aah 554h 55h aaah 80h aaah aah 554h 55h aaah 10h 4 product id entry aaah aah 554h 55h aaah 90h 5 product id exit xxh f0h product id exit aaah aah 554h 55h aaah f0h 6 read protect set aaah aah 554h 55h aaah a5h 77eh f0h (note3) write protect set aaah aah 554h 55h aaah a5h 77eh 0fh (note3) table 13-21 hardware sequence flags status d7 d6 during auto opera- tion single word program d7 toggle sector erase/chip erase 0 toggle read protect set/write protect set cannot be used toggle
page 232 2007-10-10 tmp91fu62 13.6.1 single word program the single word program command sequence programs the flash memory on a word basis. the address and data to be programmed are specified in the 4th bus write cycle. it takes a maximum of 60 us to program a sin- gle word. another command sequence cannot be executed until the write operation has completed. this can be checked by reading the same address in the flash memory repeatedly until the same data is read consecutively. while a write operation is in progress, bit 6 of data is t oggled each time it is read. note:to rewrite data to flash memory addresses at which dat a (including ffffh) is already written, make sure to erase the existing data by ?sector erase? or ?chip erase? before rewriting data. 13.6.2 sector erase (8-kbyte erase) the sector erase command sequence erases 8 kbytes of data in the flash memory at a time. the flash mem- ory address range to be erased is specified in the 6th bus write cycle. for the addr ess range of each sector, see table 13-3. this command sequence cannot be used in programmer mode. it takes a maximum of 75 ms to erase 8 kbytes. another command sequence cannot be executed until the erase operation has completed. this can be checked by reading the same address in the flash memory repeat- edly until the same data is read consecutively. while a erase operation is in progress, bit 6 of data is toggled each time it is read. 13.6.3 chip erase (all erase) the chip erase command sequence erases the entire area of the flash memory. it takes a maximum of 300 ms to erase the entire flash memory. another command sequence cannot be exe- cuted until the erase operation has completed. this can be checked by reading the same address in the flash memory repeatedly until the same data is read consecu tively. while a erase operati on is in progress, bit 6 of data is toggled each time it is read. erase operations clear data to ffh. 13.6.4 product id entry when the product id entry command is executed, product id mode is entered. in this mode, the vendor id, flash macro id, flash size id, and read/write protect status can be read from the flash memory. in product id mode, the data in the flash memory cannot be read. 13.6.5 product id exit this command sequence is used to exit product id mode.
page 233 2007-10-10 tmp91fu62 13.6.6 read protect set the read protect set command sequence applies read protection on the flash memo ry. when read protection is applied, the flash memory cannot be read in pr ogrammer mode and the ram transfer command cannot be executed in single boot mode. to cancel read protection, it is n ecessary to execute the chip erase co mmand sequence. to check whether or not read protection is applied, read xxx77eh in product id mode. it takes a maximum of 60 us to set read pro- tection on the flash memory. another command sequence cannot be executed until th e read protection setting has completed. this can be checked by reading the same address in the fl ash memory repeatedly until the same data can be read consecutively. while a read protect oper ation is in progress, bit 6 of data is toggled each time it is read. 13.6.7 write protect set the write protect set command sequence applies write protection on the flash memory. when write protec- tion is applied, the flash memory cannot be written to in programmer mode and the ram transfer command cannot be executed in single boot mode. to cancel write protection, it is ne cessary to execute the chip erase command sequence. to check whether or not write protection is applied, read xxx77eh in product id mode. it takes a maximum of 60 us to set write protection. another command sequence cannot be executed until the write protection setting has completed. this can be checked by reading the same address in th e flash memory repeatedly until the same data can be read consecutively. while a write protect operation is in progress, bit 6 of data is togg led each time it is read. 13.6.8 hardware sequence flags the following hardware sequence flags are available to check the auto oper ation execution status of the flash memory. 1. data polling (d7) when data is written to the flash memory, d7 ou tputs the complement of its programmed data until the write operation has completed. after the writ e operation has completed, d7 outputs the proper cell data. by reading d7, therefor e, the operation status can be checked. while the sector erase or chip erase command sequence is being executed, d7 outputs ?0?. after the command sequence is completed, d7 outputs ?1? (cell data). then, the data written to all the bits can be read after waiting for 1 us. when read/write protection is applied, the data polling function cannot be used. instead, use the toggle bit (d6) to check the operation status. 2. toggle bit (d6) when the flash memory program, sector erase, chip erase, write pr otect set, or read protect set command sequence is executed, bit 6 (d6) of the da ta read by read operat ions outputs ?0? and ?1? alternately each time it is read until the processing of the executed command sequence has com- pleted. the toggle bit (d6) thus provides a software means of checking whether or not the processing of each command sequence has comple ted. normally, the same addre ss in the flash memory is read repeatedly until the same data is read successively. the initial read of the to ggle bit always returns ?1?. note:the flash memory incorporated in the tmp91fu62 does not have an exceed-time-limit bit (d5). it is therefore necessary to set the data polling time limit and toggle bi t polling time limit so that polling can be stopped if the time limit is exceeded.
page 234 2007-10-10 tmp91fu62 13.6.9 data read data is read from the flash memory in byte units or word units. it is not nece ssary to execute a command sequence to read data from the flash memory. 13.6.10programming the flash me mory by the internal cpu the internal cpu programs the flash memory by using the command sequences and hardware sequence flags described above. however, since the flash memory canno t be read during auto op eration mode, the program/ erase routine must be executed outside of the flash memory. the cpu can program the flash memory either by using single boot mode or by using a user-created proto- col in single chip mode (user boot). 1. single boot: the microcontroller is started up in single boot mode to program the flash memory by the internal boot rom program. in this mode, the internal boot rom is mapped to an area including the interrupt vector table, in which the boot rom program is ex ecuted. the flash memory is mapped to an address area different from the boot rom area. the boot ro m program loads data into the flash memory by serial transfer. in single boot mode, interrupts must be disabled including non-maskable interrupts. for details, see " 13.4 single boot mode " 2. user boot: in this method, the flash memory is programme d by executing a user-cr eated routine in single chip mode (normal operation mode). in this mode, the user-created program/ erase routine must also be executed outside of the flash memory. it is also necessary to disable interrupts including non- maskable interrupts. the user should prepare a flash memory program/e rase routine (including routines for loading write data and writing the loaded data into the flas h memory). in the main program, normal operation is switched to flash memory pr ogramming operation to execute th e flash memory program/erase rou- tine outside of the flash memory area. for example, the flash me mory program/erase routine may be transferred from the flash memory to the internal ram and executed there or it may be prepared and executed in external memory. for details, see " 13.5 user boot mode (in single chip mode) ".
page 235 2007-10-10 tmp91fu62 flowcharts: flash memory access by the internal cpu single word program 2tqitcoeqoocpfugswgpeg (see the flowchart below) 5vctv 6qiingdkv
& .cuvcfftguu! no yes 2tqitcogpf address = address + 2 (even-numbered address/ word units) 2tqitco%qoocpf5gswgpeg
#fftguu&cvc xxxaaah/aah xxx554h/55h xxxaaah/a0h 'xgppwodgtgfrtqitcocfftguu
# rtqitcofcvc
yqtfwpkvu 4gcffcvcocvejgf rtqitcofcvc! #dpqtocngpf yes yes no no timeout(60
? s) 9qtftgcf addr. = 2tqitcocfftguu 9qtftgcf addr. = 2tqitcocfftguu 4gcffcvcocvejgf rtqitcofcvc!
page 236 2007-10-10 tmp91fu62 chip erase/sector erase  %jkr'tcug%qoocpf5gswgpeg
#fftguu&cvc  zzz###*##*  zzz ** zzz###**  zzz###*##*  zzz** zzz###**  5gevqt'tcug%qoocpf5gswgpeg
#fftguu&cvc  zzz###*##*  zzz* *  zzz###**  zzz###*##*  zzz ** 5gevqtcfftguu*  'tcugeqoocpfugswgpeg
5ggvjghnqyejctvdgnqy   5vctv  6iingdkv
&  'tcuggpf   4gcffcvcdncpm! 
0qvg #dpqtocngpf ;gu  0q  6kogqwv 
%jkrou5gevqtou 0qvg+p%jkr'tcugyjgvjgtqtpqvvjggpvktghncujogoqt[kudncpmkuejgemgf +p5gevqt'tcugyjgvjgtqtpqvvjgugngevgfugevqtkudncpmkuejgemgf
page 237 2007-10-10 tmp91fu62 read/write protect set protect set command sequence (address/data) xxxaaah/aah xxx554h/55h xxxaaah/a5h set read protect xxx77eh/f0h set write protect xxx77eh/0fh set both read protect and write protect xxx77eh/00h protect set command sequence (see the flowchart below) start toggle bit (d6) protect set end abnormal end yes timeout (60 s) product id entry read data matched p ro g ram data? product id exit byte read (d7 to d0) addr. = xxx77eh no toggle bit (d6) protect set command sequence (see the flowchart below) product id entry product id exit
page 238 2007-10-10 tmp91fu62 data polling (d7) toggle bit (d6) note:hardware sequence flags are read from the flash memory in byte units or word units. va:in single word program, va denotes the address to be programmed. in sector erase, va denotes any address in the selected sector. in chip erase, va denotes an y address in the flash memory. in read protect set, va denotes the protect set address (xx77eh). in write protect set, va denotes the protect set address (xx77eh).  $[vgtgcf
&:*&  #fft8# 5vctv  &&cvc! ;gu 0q 
8#8cnkf#fftguu  1rgtcvkqpgpf 
0qvg $[vgtgcf
&vq&0qvg #fft8# & 6qiing ! 5vctv  0q  1rgtcvkqpgpf ;gu  #fft8# $[vgtgcf
&vq&0qvg
page 239 2007-10-10 tmp91fu62 product id entry product id exit  zzz **  5vctv  zzz###*##* zzz ###** 9ckvhqtpugeqtnqpigt
+&#eeguucpf'zkv6kog/czpuge ???:2tqfwev+&oqfguvctv:     2tqfwev+&tgcf 
5ggvjgvcdngdgnqy  4gcf8cnwgukp2tqfwev+&/qfg   #fftguu 4gcf8cnwg 8gpfqt+&  zzzz*  *  (ncujocetq+&  zzzz*  *  (ncujuk\g+&  zzzz*  *  4gcf9tkvg  2tqvgevuvcvwu  zzz'*  &cvcrtqitcoogfyjgprtqvgevkqpkuugv 9jgprtqvgevkqpkupqvugv((*   5vctv  zzz###* ##*  zzz* *  zzz###*(*    zzzzzz*(*     2tqfwev+&oqfggpf   5vctv 9ckvhqtpugeqtnqpigt
+&#eeguucpf'zkv6kog/czpuge 9ckvhqtpugeqtnqpigt
+&#eeguucpf'zkv6kog/czpuge 2tqfwev+&oqfggpf
page 240 2007-10-10 tmp91fu62 (example: program to be lo aded and executed in ram) erase the flash memory (chip erase) a nd then write 0706h to address fe8000h. ;#### flash memory ch ip erase processing #### ld xix, 0xfe8000 ; set start address chiperase: ld (0xfe8aaa), 0xaa ;1st bus write cycle ld (0xfe8554), 0x55 ;2nd bus write cycle ld (0xfe8aaa), 0x80 ;3rd bus write cycle ld (0xfe8aaa), 0xaa ;4th bus write cycle ld (0xfe8554), 0x55 ;5th bus write cycle ld (0xfe8aaa), 0x10 ;6th bus write cycle cal togglechk ; check toggle bit chiperase _ loop: ld wa, (xix+) ; read data from flash memory cp wa, 0xffff ; blank data? j ne,chiperase _ err ; if not blank data, jump to error processing cp xix, 0xffffff ; end address (0xffffff)? j ult,chiperase _ loop ; check entire memory area and then end loop processing ;#### flash memory program processing #### ld xix, 0xfe8000 ; set program address ld wa, 0x0706 ; set program data program: ld (0xfe8aaa), 0xaa ;1st bus write cycle ld (0xfe8554), 0x55 ;2nd bus write cycle ld (0xfe8aaa), 0xa0 ;3rd bus write cycle ld (xix), wa ;4th bus write cycle cal togglechk ; check toggle bit ld bc, (xix) ; read data from flash memory cp wa, bc j ne, program _ err ; if programmed data cannot be read, error is determined ld bc, (xix) ; read data from flash memory cp wa, bc j ne, program _ err ; if programmed data cannot be read, error is determined program _ end: j program _ end ; program operation end
page 241 2007-10-10 tmp91fu62 ;#### toggle bit (d6) check processing #### togglechk: ld l, (xix) and l, 0y01000000 ; check toggle bit (d6) ld h, l ; save first toggle bit data togglechk1: ld l, (xix) and l, 0y01000000 ; check toggle bit (d6) cp l, h ; toggle bit = toggled? j z, togglechk2 ; if not toggled, end processing ld h, l ; save current toggle bit state j togglechk1 ; recheck toggle bit togglechk2: ret ;#### error processing #### chiperase _ err: j chiperase _ err ; chip erase error program _ err: j program _ err ; program error
page 242 2007-10-10 tmp91fu62 (example: program to be lo aded and executed in ram) erase data at addresses ff0000h to ff1fffh (sector erase) and then write 0706h to address ff0000h. ;#### flash memory sector erase processing #### ld xix, 0xff0000 ; set start address sectorerase: ld (0xfe8aaa), 0xaa ;1st bus write cycle ld (0xfe8554), 0x55 ;2nd bus write cycle ld (0xfe8aaa), 0x80 ;3rd bus write cycle ld (0xfe8aaa), 0xaa ;4th bus write cycle ld (0xfe8554), 0x55 ;5th bus write cycle ld (xix), 0x30 ;6th bus write cycle cal togglechk ; check toggle bit sectorerase _ loop: ld wa, (xix+) ; read data from flash memory cp wa, 0xffff ; blank data? j ne,sectorerase _ err ; if not blank data, jump to error processing cp xix, 0xff1fff ; end address (0xff1fff)? j ult,sectorerase _ loop ; check erased sector area and then end loop processing ;#### flash memory program processing #### ld xix, 0xff0000 ; set program address ld wa, 0x0706 ; set program data program: ld (0xfe8aaa), 0xaa ;1st bus write cycle ld (0xfe8554), 0x55 ;2nd bus write cycle ld (0xfe8aaa), 0xa0 ;3rd bus write cycle ld (xix), wa ;4th bus write cycle cal togglechk ; check toggle bit ld bc, (xix) ; read data from flash memory cp wa, bc j ne, program _ err ; if programmed data cannot be read, error is determined ld bc, (xix) ; read data from flash memory cp wa, bc j ne, program _ err ; if programmed data cannot be read, error is determined program _ end: j program _ end ; program operation end
page 243 2007-10-10 tmp91fu62 ;#### toggle bit (d6) check processing #### togglechk: ld l, (xix) and l, 0y01000000 ; check toggle bit (d6) ld h, l ; save first toggle bit data togglechk1: ld l, (xix) and l, 0y01000000 ; check toggle bit (d6) cp l, h ; toggle bit = toggled? j z, togglechk2 ; if not toggled, end processing ld h, l ; save current toggle bit state j togglechk1 ; recheck toggle bit togglechk2: ret ;#### error processing #### sectorerase _ err: j sectorerase _ err ; sector erase error program _ err: j program _ err ; program error
page 244 2007-10-10 tmp91fu62 (example: program to be lo aded and executed in ram) set read protection and write protection on the flash memory. ;#### flash memory protect set processing #### ld xix, 0xfe877e ; set protect address protect: ld (0xfe8aaa), 0xaa ;1st bus write cycle ld (0xfe8554), 0x55 ;2nd bus write cycle ld (0xfe8aaa), 0xa5 ;3rd bus write cycle ld (xix), 0x00 ;4th bus write cycle cal togglechk ; check toggle bit cal pid _ entry ; ld a, (xix) ; read protected address cal pid _ exit ; cp a, 0x00 ;(0xfe877e)=0x00? j ne, protect _ err ; protected? protect _ end: j protect _ end ; protect set operation completed protect _ err: j protect _ err ; protect set error ;#### product id entry processing #### pid _ entry: ld (0xfe8aaa), 0xaa ;1st bus write cycle ld (0xfe8554), 0x55 ;2nd bus write cycle ld (0xfe8aaa), 0x90 ;3rd bus write cycle ; --- wait for 300 nsec or longer (execute nop instruction [200nsec/@f fph =20mhz] two times) --- nop nop ; wait for 400 nsec ret ;#### product id exit processing #### pid _ exit: ld (0xfe8000), 0xf0 ;1st bus write cycle ; --- wait for 300 nsec or longer (execute nop instruction [200nsec/@f fph =20mhz] two times) --- nop nop ; wait for 400 nsec ret
page 245 2007-10-10 tmp91fu62 (example: program to be lo aded and executed in ram) read data from address fe8000h. ;#### toggle bit (d6) check processing #### togglechk: ld l, (xix) and l, 0y01000000 ; check toggle bit (d6) ld h, l ; save first toggle bit data togglechk1: ld l, (xix) and l, 0y01000000 ; check toggle bit (d6) cp l, h ; toggle bit = toggled? j z, togglechk2 ; if not toggled, end processing ld h, l ; save current toggle bit state j togglechk1 ; recheck toggle bit togglechk2: ret ;#### flash memory read processing #### read: ld wa, (0xfe8000) ; read data from flash memory
page 246 2007-10-10 tmp91fu62 14. electrical characteristics 14.1 absolute maximum ratings note: absolute maximum ratings are limiti ng values of operating and environmental conditions which should not be exceeded under the worst possible conditions. the equipment manufacturer should design so that no absolute maximum rating value is exceeded. exposure to conditions beyond those listed above may cause per manent damage to the device or affect device reliability, which could increase potential risks of personal injury due to ic blowup and/or burning. parameter symbol pin name rating unit supply voltage v cc ? 0.5 to 6.0 v input voltage v in ? 0.5 to v cc + 0.5 v output current (per pin) i ol1 p5, p6, p96, p97 2 ma output current (per pin) i ol2 p1, p3, p4, p7, p8, p90-p95, pa, pb 5m a output current (per pin) i ol3 p0 30 ma output current (per pin) i oh1 p5, p6, p96, p97 ? 2ma output current (per pin) i oh2 p1, p3, p4, p7, p8, p90-p95, pa, pb ? 5m a output current (per pin) i oh3 p0 ? 30 ma output current (total) i ol p1, p3, p4, p5, p6, p7, p8, p9, pa, pb 80 ma output current (total) i oh p1, p3, p4, p5, p6, p7, p8, p9, pa, pb ? 80 ma output current (high current port total) i ol3 p0 120 ma output current (high current port total) i oh3 p0 ? 120 ma power dissipation (t opr = 85 c) pd 600 mw soldering temperature (10 s) t solder 260 c storage temperature t stg ? 65 to 150 c operating temperature t opr ? 40 to 85 c solderability of lead free products test parameter test condition note solderability use of sn-37pb solder bath solder bath temperature 230 c, dipping time 5 [s] the number of times one, use of r-type flux pass: solderability rate until forming 95% use of sn-3.0ag-0.5 cu solder bath solder bath temperature 245 c, dipping time 5 [s] the number of times one, use of r-type flux (use of lead free)
page 247 2007-10-10 tmp91fu62 14.2 dc electrical characteristics note 1: typical values show those at t opr = 25 c and v cc = 5 v. note 2: i cc measurement conditions (normal, sl ow): all functions are operational; ou tput pins are open and input pins are level fixed. data and address bus cl = 30 pf loaded. note 3: when a program is executing in the flash memory or when data is being read from the flash memory, the flash memory operates in an intermittent manner, causing peak curr ents in the operation current, as shown in figure 14-1. in this case, the supply current i cc (in normal and slow modes) is defined as the sum of the average peak current and mcu current. parameter symbol condition min typ. max unit power supply voltage (av cc = dv cc ) (av ss = dv ss = 0v) v cc fc = 4 to 20 mhz fs = 30 to 34 khz 4.5 5.5 v for erase/program operations of flash memory (av cc = dv cc ) (av ss = dv ss = 0v) fc = 4 to 20 mhz t opr = -10 to 4 0 c 4.75 5.25 low-level input volt- age p00 to p17 v il v cc = 4.5 to 5.5 v ? 0.3 0.8 v reset , p30 to pb2 v il1 0.25 v cc am0, am1 v il2 0.3 x1 v il3 0.2 v cc high-level input volt- age p00 to p17 v ih v cc = 4.5 to 5.5 v 2.2 v cc + 0.3 v reset , p30 to pb2 v ih2 0.75 v cc am0, am1 v ih3 v cc ? 0.3 x1 v ih4 0.8 v cc low-level output voltage v ol i ol = 1.6 ma (v cc = 4.5 to 5.5 v) 0.45 v high-level output voltage v oh i oh = ? 400 a (v cc = 4.5 to 5.5 v) 4.2 v i oh = ? 1.6 ma (v cc = 4.5 to 5.5 v) 2.4 low-level output current high current port p0 i ol v ol = 1.0v (v cc = 4.5 to 5.5 v) 20 ma input leakage current i li 0.0 v in v cc 0.02 5 a output leakage current i lo 0.2 v in v cc ? 0.2 0.05 10 power down voltage (while ram is being backed up in stop mode) v stop v il2 = 0.2 v cc v ih2 = 0.8 v cc 2.0 5.5 v reset pull-up resistor r rst v cc = 4.5 to 5.5 v 50 230 k pin capacitance c io fc = 1 mhz 10 pf schmitt width reset , int0 v th v cc = 4.5 to 5.5 v 0.4 1.0 v programmable pull-up resistor rkh v cc = 4.5 to 5.5 v 50 230 k normal (note 2) i cc v cc = 4.5 to 5.5 v fc = 20 mhz 25 35 ma idle2 81 5 idle1 3.5 8 slow (note 2) v cc = 4.5 to 5.5 v fs = 32.768 khz 80 100 a stop t opr 50 c v cc = 4.5 to 5.5 v 0.5 10 a t opr 70 c 25 t opr 85 c 50 peak current for intermittent operation (note 3,4) i ddp-p v dd = 5.5 v ? 20 ? ma
page 248 2007-10-10 tmp91fu62 note 4: when designing the power supply, make sure that p eak currents can be supplied. in slow1 mode, the difference between the peak current and the average current becomes large. figure 14-1 intermittent operation of flash memory n program coutner (pc) n+1 n+2 n+3 1 machine cycle (4/fc or 4/fs) mcu current i [ma] ddp-p typ. current momentary flash current max. current sum of average momentary flash current and mcu current
page 249 2007-10-10 tmp91fu62 14.3 ad conversi on characteristics note 1: 1lsb = (av cc - av ss )/1024 [v] note 2: the operation above is guaranteed for ffph 4 mhz. note 3: the value for i cc includes the current which flows through the a v cc pin. av cc = dv cc , av ss = dv ss parameter symbol variable min typ. max unit analog reference voltage ( + ) av cc v cc = 4.5 to 5.5 v dv cc - 1.5 v dv cc dv cc v analog reference voltage ( - ) av ss dv ss dv ss dv ss + 0.2 v v analog input voltage range v ain av ss av cc v error (not including quantizing errors) - 1.0 4.0 lsb
page 250 2007-10-10 tmp91fu62 14.4 serial channel timi ng (i/o internal mode) 14.4.1 sclk input mode note: symbol ?x? in the above tabl e means the period of clock ?f fph ?, it?s half period of the system clock ?f sys ? for cpu core. the period of f fph depends on the clock gear setting or the selection of high-/low-oscillator frequency. 14.4.2 sclk output mode note 1: *: sclk rising/falling edge:the rising edge is used in sclk rising mode. the falling edge is used in sclk falling mode. note 2: 20 mhz and 16 mhz values are calculated from t scy = 16x case. note 3: symbol ?x? in the above table means the period of clock ?f fph ?, it?s half period of the system clock ?f sys ? for cpu core. the period of f fph depends on the clock gear setting or the se lection of high-/low-oscillator frequency. parameter symbol variable 20 mhz 16 mhz unit min max min max min max sclk period t scy 16x 800 1000 ns output data sclk rising/falling edge* t oss t scy /2 ? 4x ? 85 (v cc = 5v 10%) 115 165 ns sclk rising/falling edge* output data hold t ohs t scy /2 + 2x + 0 500 625 ns sclk rising/falling edge* input data hold t hsr 3x + 10 160 198 ns sclk rising/falling edge* valid data input* t srd t scy ? 0 800 1000 ns valid data input sclk rising/falling edge* t rds 00 0 n s parameter symbol variable 20 mhz 16 mhz unit min max min max min max sclk period t scy 16x 8192x 0.8 410 1.0 512 s output data sclk rising/falling edge* t oss t scy /2 ? 40 360 460 ns sclk rising/falling edge* output data hold t ohs t scy /2 ? 40 360 460 ns sclk rising/falling edge* input data hold t hsr 00 0 n s sclk rising/falling edge* valid data input t srd t scy ? 1x ? 90 660 847 ns valid data input sclk rising/falling edge* t rds 1x + 90 140 153 ns 0123 0123 valid valid valid valid output data txd input data rxd sclk (rising edge) sclk (falling edge) t oss t srd t scy t rds t hsr t ohs
page 251 2007-10-10 tmp91fu62 14.5 event counter ta0in, ta4in, tb0in0, tb0in1, tb1in0,t b1in1, tb2in0,tb2in1, tb3in0,tb3in1 note: symbol ?x? in the above tabl e means the period of clock ?f fph ?, it?s half period of the system clock ?f sys ? for cpu core. the period of f fph depends on the clock gear setting or the selection of high-/low-oscillator frequency. parameter symbol variable 20 mhz 16 mhz unit min max min max min max clock period t vck 8x + 100 500 600 ns clock low-level width t vckl 4x + 40 240 290 ns clock high-level width t vckh 4x + 40 240 290 ns
page 252 2007-10-10 tmp91fu62 14.6 interrupt and capture 14.6.1 int0 to int4 interrupts note: symbol ?x? in the above tabl e means the period of clock ?f fph ?, it?s half period of the system clock ?f sys ? for cpu core. the period of f fph depends on the clock gear setting or the selection of high-/low-oscillator frequency. 14.6.2 int1 to int8 interrupts, capture int1 to int8 input pulse width depend on the system clock selection and clock selection for prescaler. below table show pulse width of each operation clock. note 1: ?xc? shows period of clock fc in high frequency oscillator. note 2: symbol ?x? in the above table means the period of clock ?f fph ?, it?s half period of the system clock ?f sys ? for cpu core. the period of f fph depends on the clock gear setting or the se lection of high-/low-oscillator frequency. parameter symbol variable 20 mhz 16 mhz unit min max min max min max int0 to int4 low-level width t intal 4x + 40 240 290 ns int0 to int4 high-level width t intah 4x + 40 240 290 ns system clock selection syscr1 clock selection for prescaler syscr0 t intbl (int1 to int8 low level pulse width) t intbh (int1 to int8 high level pulse width) unit variable f fph = 20mhz variable f fph = 20 mhz min min min min 0 (fc) 0 (f fph ) 8x + 100 500 8x + 100 500 ns 1 (fc/16) 128xc + 0.1 6.5 128xc + 0.1 6.5 us 1 (fc) 0 (f fph ) 8x + 0.1 244.3 8x + 0.1 244.3
page 253 2007-10-10 tmp91fu62 14.7 scout pin ac characteristics note: t = period of scout measuring conditions output level: high = 0.7 v cc , low = 0.3 v cc , cl = 10 pf 14.8 flash characteristics 14.8.1 write/retenti on characteristics parameter symbol variable 20 mhz 16 mhz condition unit min max min max min max low-level width t sch 0.5t ? 15 10 16 v cc 4.5v ns high-level width t scl 0.5t ? 15 10 16 v cc 4.5v ns (v ss = 0 v) parameter condition min typ. max. unit number of guaranteed writes to flash memory v ss = 0 v fc = 4 to 20 mhz t opr = ? 10 to 40 c ?? 100 times t sch t scl scout
page 254 2007-10-10 tmp91fu62 14.9 recommended oscillating conditions the tmp91fu62 has been evaluated by the oscillator vender below. use this information when selecting external parts. note 1: to ensure stable oscillation, the re sonator position, load capacitance, etc. must be appropriate. because these factors are greatly affected by board patterns, please be sure to evaluate operation on the board on which the device will actually be mounted. note 2: when using the device (oscillator) in places exposed to high elec tric fields such as cathode-ray tubes, we recommend electrically shielding the package in order to maintain normal operating condition. note 3: the product numbers and specifications of the resonators by murata manufacturing co., ltd. are subject to change. for up-to-date information, please refer to the following url: http://www.murata.co.jp/search/index.html x1 x2 c 2 rd c 1 xt1 xt2 c 2 rd c 1 (2) low-frequency oscillation (1) high-frequency oscillation
page 255 2007-10-10 tmp91fu62 15. table of sfr?s the special function registers (sfrs) include the i/o ports and peripheral cont rol registers allocated to the 4-kbyte address space from 000000h to 000fffh. 1. i/o ports 2. i/o port control 3. interrupt control 4. clock gear 5. 8-bit timer 6. 16-bit timer 7. uart/serial channel 8. i 2 c bus interface 9. ad converter 10. watchdog timer 11. special timer for clock 12. program patch logic
page 256 2007-10-10 tmp91fu62 note: do not access to the unnamed addresses (e.g., addresses to which no register has been allocated). table 15-1 sfr address map (port, intc, cs/wait) [1]port address name address name address name 0000h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh p0 p1 p0cr p1cr p3 p3fc2 p3cr p3fc 0010h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh p4 p4fc2 p4cr p5 siochg1 p5cr p5fc p6 p6cr p6fc p7 p7cr p7fc 0020h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh p8 p8cr p8fc p9 siochg0 p9cr p9fc pa pacr pafc pb pbcr [2]intc [2]intc address name address name address name 0030h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh ode 0080h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh dma0v dma1v dma2v dma3v intclr dmar dmab iimc 0090h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh inte0ad inte12 inte34 inte56 inte78 inteta01 inteta45 intetb0 intetb1 intetb2 intetb3 intetb01v intetb23v [4] cgear address name address name 00a0h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh intertc intes0 intes1 intes2 intesbi0 intetc01 intetc23 00e0h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh syscr0 syscr1 syscr2 emccr0 emccr1
page 257 2007-10-10 tmp91fu62 note: do not access to the unnamed addresses (e.g., addresses to which no register has been allocated). table 15-2 sfr address map (cgcr, tmra, tmrb) [5] tmra [6] tmrb address name address name address name 0100h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh ta01run ta0reg ta1reg ta01mod ta1ffcr 0110h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh ta45run ta4reg ta5reg ta45mod ta5ffcr 0180h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh tb0run tb0mod tb0ffcr tb0rg0l tb0rg0h tb0rg1l tb0rg1h tb0cp0l tb0cp0h tb0cp1l tb0cp1h [6] tmrb address name address name address name 0190h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh tb1run tb1mod tb1ffcr tb1rg0l tb1rg0h tb1rg1l tb1rg1h tb1cp0l tb1cp0h tb1cp1l tb1cp1h 01a0h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh tb2run tb2mod tb2ffcr tb2rg0l tb2rg0h tb2rg1l tb2rg1h tb2cp0l tb2cp0h tb2cp1l tb2cp1h 01b0h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh tb3run tb3mod tb3ffcr tb3rg0l tb3rg0h tb3rg1l tb3rg1h tb3cp0l tb3cp0h tb3cp1l tb3cp1h [7] uart/sio [8] i 2 c address name address name address name 0200h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh sc0buf sc0cr sc0mod0 br0cr br0add sc0mod1 sc1buf sc1cr sc1mod0 br1cr br1add sc1mod1 0210h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh sc2buf sc2cr sc2mod0 br2cr br2add sc2mod1 0240h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh sbi0cr1 sbi0dbr i2c0ar sbi0cr2/sbi0sr sbi0br sbi0cr0
page 258 2007-10-10 tmp91fu62 note: do not access to the unnamed addresses (e.g., addresses to which no register has been allocated). table 15-3 sfr address map (uart/sio, i 2 c, adc, wdt, rtc, romc) [9]10bit adc [10] wdt [11] rtc address name address name address name 02b0h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh adccr1 adccr2 adcdrl adcdrh 0300h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh wdmod wdcr 0310h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh rtccr [12] romc address name address name address name 0400h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh romcmp00 romcmp01 romcmp02 romsub0l romsub0h romcmp10 romcmp11 romcmp12 romsub1l romsub1h 0410h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh romcmp20 romcmp21 romcmp22 romsub2l romsub2h romcmp30 romcmp31 romcmp32 romsub3l romsub3h 0420h 1h 2h 3h 4h 5h 6h 7h 8h 9h ah bh ch dh eh fh romcmp40 romcmp41 romcmp42 romsub4l romsub4h romcmp50 romcmp51 romcmp52 romsub5l romsub5h
page 259 2007-10-10 tmp91fu62 (1) i/o ports symbol name address 7 6 5 4 3 2 1 0 p0 port 0 00h p07 p06 p05 p04 p03 p02 p01 p00 r/w data from external port (output latch register is undefined.) p1 port 1 01h p17 p16 p15 p14 p13 p12 p11 p10 r/w data from external port (output latch register is cleared to ?0?.) p3 port 3 0ch ????p 3 3p 3 2p 3 1p 3 0 ???? r / w ???? data from external port (output latch register is set to ?1?.) p4 port 4 10h ????p 4 3p 4 2p 4 1p 4 0 r/w ???? data from external port (output latch register is set to ?1?.) ???? 0 (output latch register): pull-up resistor off 1 (output latch register): pull-up resistor on p5 port 5 14h p57 p56 p55 p54 p53 p52 p51 p50 r/w data from external port (output latch register is set to ?1?.) p6 port 6 18h p67 p66 p65 p64 p63 p62 p61 p60 r/w data from external port (output latch register is set to ?1?.) p7 port 7 1ch ? ? p75 p74 p73 p72 p71 p70 ?? ? ? ? data from external port (outpu t latch register is set to ?1?.) p8 port 8 20h p87 p86 p85 p84 p83 p82 p81 p80 r/w data from external port (output latch register is set to ?1?.) p9 port 9 24h p97 p96 p95 p94 p93 p92 p91 p90 r/w data from external port (output latch register is set to ?1?.) pa port a 28h ? ? ? ? pa3 pa2 pa1 pa0 ???? r / w ???? data from external port (output latch register is set to ?1?.) pb port b 2ch ? ? ? ? ? pb2 pb1 pb0 ????? r / w ????? data from external port (output latch register is set to ?1?.)
page 260 2007-10-10 tmp91fu62 (2) i/o port control symbol name address 7 6 5 4 3 2 1 0 p0cr port 0 control 02h (rmw instruc- tions are pro- hibited.) p07c p06c p05c p04c p03c p02c p01c p00c w 00000000 0: input 1: output p1cr port 1 control 04h (rmw instruc- tions are pro- hibited.) p17c p16c p15c p14c p13c p12c p11c p10c w 00000000 0: input 1: output p3cr port 3 control 0eh (rmw instruc- tions are pro- hibited.) ? ? ? ? p33c p32c p31c p30c ???? w ????0000 ???? <> <> p3fc port 3 function 0fh (rmw instruc- tions are pro- hibited.) ? ? ? ? p33f p32f p31f p30f ???? w ????0000 ???? p33f/ p33c= 00:input port 01:output port 10: reserv ed 11: tb3out1 p32f/ p32c= 00:input port 01:output port 10: reserv ed 11: tb3out0 <> p3fc2 port 3 function 2 0dh (rmw instruc- tions are pro- hibited.) ??????p 3 1 f 2p 3 0 f 2 ?????? w ??????00 ?????? p31f2/ p31f/ p31c= 000:input port 001:output port 010: tb3in1 /int4 101: scl0 p30f2/ p30f/ p30c= 000:input port 001:output port 010: tb3in0 /int3 101: sda0
page 261 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 p4cr port 4 control 12h (rmw instruc- tions are pro- hibited.) ? ? ? p44c p43c p42c p41c p40c ??? w ???00000 ? ? ? <> p4fc2 port 4 function 2 11h (rmw instruc- tions are pro- hibited.) ? ? ? ? p43f2 ? p41f2 p40f2 ????w? w ????0?00 ???? p43f2, p43c = 00 :input port 01:output port 10: reserved 11:sclk2 p42c = 0: input port 1: output port p41f2, p41c = 00: input port 01: output port 10: reserved 11:txd2 p40f2, p40c = 00: input port 01:output port 10: reserved 11: scout siochg1 sio change register 1 15h (rmw instruc- tions are pro- hibited.) ??? siochg14 ? siochg12 siochg11 ? ???w? w ? ???0?00? ??? p42 port 0: cmos output 1: open- drain output ? 0: setting of p42c 1: txd2 0: setting of p41f2 and p41c 1: rxd2 ? p5cr port 5 control 16h (rmw instruc- tions are pro- hibited.) p57c p56c p55c p54c p53c p52c p51c p50c w 00000000 0: input 1: output p5fc port 5 function 17h (rmw instruc- tions are pro- hibited.) p57f p56f p55f p54f p53f p52f p51f p50f w 00000000 p57 input 0: disable 1: enable p56 input 0: disable 1: enable p55 input 0: disable 1: enable p54 input 0: disable 1: enable p53 input 0: disable 1: enable p52 input 0: disable 1: enable p51 input 0: disable 1: enable p50 input 0: disable 1: enable p6cr port 6 control 1ah (rmw instruc- tions are pro- hibited.) p67c p66c p65c p64c p63c p62c p61c p60c w 00000000 0: input 1: output p6fc port 6 function 1bh (rmw instruc- tions are pro- hibited.) p67f p66f p65f p64f p63f p62f p61f p60f w 00000000 p67 input 0: disable 1: enable p66 input 0: disable 1: enable p65 input 0: disable 1: enable p64 input 0: disable 1: enable p63 input 0: disable 1: enable p62 input 0: disable 1: enable p61 input 0: disable 1: enable p60 input 0: disable 1: enable p7cr port 7 control 1eh (rmw instruc- tions are pro- hibited.) ? ? p75c p74c p73c p72c p71c p70c ?? w ??000000 ? ? 0: input 1: output p7fc port 7 function 1fh (rmw instruc- tions are pro- hibited.) ? ? p75f p74f ? ? p71f ? ?? w ??w? ??00??0? ?? 0: port 1: int0 0: port 1: ta5out ?? 0: port 1: ta1out ?
page 262 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 p8cr port 8 control 22h (rmw instruc- tions are pro- hibited.) p87c p86c p85c p84c p83c p82c p81c p80c w 00000000 0: input 1: output p8fc port 8 function 23h (rmw instruc- tions are pro- hibited.) p87f p86f p85f p84f p83f p82f p81f p80f w 00000000 0: port 1: tb1out1 0: port 1: tb1out0 0: port 1: tb1in1, int8 0: port 1: tb1in0, int7 0: port 1: tb0out1 0: port 1: tb0out0 0: port 1: tb0in1, int6 0: port 1: tb0in0, int5 siochg0 sio change register 0 25h (rmw instruc- tions are pro- hibited.) ?? siochg05 siochg04 siochg03 siochg02 siochg01 siochg00 ?? w ??000000 ?? p94 port 0: cmos output 1: open- drain output 0: setting of p94c 1: txd1 0: setting of p93f and p93c 1: rxd1 p91 port 0: cmos output 1: open- drain output 0: setting of p91c 1: txd0 0: setting of p90f and p90c 1: rxd0 p9cr port 9 control 26h (rmw instruc- tions are pro- hibited.) p97c p96c p95c p94c p93c p92c p91c p90c w 11000000 0: input 1: output p9fc port 9 function 27h (rmw instruc- tions are pro- hibited.) p97f p96f p95f ? p93f p92f ? p90f w?w? w 000?00?0 port 0: disable 1: enable port 0: disable 1: enable 0: port 1: sclk1 output ? 0: port 1: txd1 output 0: port 1: sclk0 output ? 0: port 1: txd0 output pacr port a control 2ah (rmw instruc- tions are pro- hibited.) ? ? ? ? pa3c pa2c pa1c pa0c ???? w ????0000 ? ? ? ? 0: input 1: output pafc port a function 2bh (rmw instruc- tions are pro- hibited.) ? ? ? ? pa3f pa2f pa1f pa0f ???? w ????0000 ???? 0: port 1: tb2out1 0:port 1: tb2out0 0: port 1: tb2in1, int2 0: port 1: tb2in0, int1 pbcr port b control 2eh (rmw instruc- tions are pro- hibited.) ? ? ? ? ? pb2c pb1c pb0c ????? w ?????000 ? ? ? ? ? 0: input 1: output ode open-drain control register 3fh ? ? ? ode93 ode90 ode41 ode31 ode30 ??? r / w ???00000 ? ? ? 0: cmos output 1:open drain output
page 263 2007-10-10 tmp91fu62 (3) interrupt control symbol name address 7 6 5 4 3 2 1 0 inte0ad interrupt enable 0 & ad 90h intad int0 iadc iadm2 iadm1 iadm0 i0c i0m2 i0m1 i0m0 rr / wrr / w 00000000 1: intad interrput level 1: int0 interrput level inte12 interrupt enable 2 / 1 91h int2 int1 i2c i2m2 i2m1 i2m0 i1c i1m2 i1m1 i1m0 rr / wrr / w 00000000 1: int2 interrput level 1: int1 interrput level inte34 interrupt enable 4 / 3 92h int4 int3 i4c i4m2 i4m1 i4m0 i3c i3m2 i3m1 i3m0 rr / wrr / w 00000000 1: int4 interrput level 1: int3 interrput level inte56 interrupt enable 6 / 5 93h int6 int5 i6c i6m2 i6m1 i6m0 i5c i5m2 i5m1 i5m0 rr / wrr / w 00000000 1: int6 interrput level 1: int5 interrput level inte78 interrupt enable 8 / 7 94h int8 int7 i8c i8m2 i8m1 i8m0 i7c i7m2 i7m1 i7m0 rr / wrr / w 00000000 1: int8 interrput level 1: int7 interrput level inteta01 interrupt enable timer a 1 / 0 96h intta1(tmra1) intta0 (tmra0) ita1c ita1m2 ita1m1 ita1m0 ita0c ita0m2 ita0m1 ita0m0 rr / wrr / w 00000000 1: intta1 interrput level 1: intta0 interrput level inteta45 interrupt enable timer a 5 / 4 98h intta5 (tmra5) intta4 (tmra4) ita5c ita5m2 ita5m1 ita5m0 ita4c ita4m2 ita4m1 ita4m0 rr / wrr / w 00000000 1: intta5 interrput level 1: intta4 interrput level
page 264 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 intetb0 interrupt enable tmrb 0 99h inttb01(tmrb0) inttb00(tmrb0) itb01c itb01m2 itb01m1 itb01m0 itb00c itb00m2 itb00m1 itb00m0 rr / wrr / w 00000000 1: inttb01 interrput level 1: inttb00 interrput level intetb1 interrupt enable tmrb 1 9ah inttb11(tmrb1) inttb10(tmrb1) itb11c itb11m2 itb11m1 itb11m0 itb10c itb10m2 itb10m1 itb10m0 rr/wrr/w 00000000 1: inttb11 interrput level 1: inttb10 interrput level intetb2 interrupt enable tmrb 2 9bh inttb21(tmrb2) inttb20(tmrb2) itb21c itb21m2 itb21m1 itb21m0 itb20c itb20m2 itb20m1 itb20m0 rr / wrr / w 00000000 1: inttb21 interrput level 1: inttb20 interrput level intetb3 interrupt enable tmrb 3 9ch inttb31(tmrb3) inttb30(tmrb3) itb31c itb31m2 itb31m1 itb31m0 itb30c itb30m2 itb30m1 itb30m0 rr / wrr / w 00000000 1: inttb31 interrput level 1: inttb30 interrput level intetb01v interrupt enable tmrb 0/1 (over flow) 9eh inttbof1(tmrb1 over flow) inttbof1(tmrb0 over flow) itf1c itf1m2 itf1m1 itf1m0 itf0c itf0m2 itf0m1 itf0m0 rr / wrr / w 00000000 1: inttbof1 interrput level 1:inttbof0 interrput level intetb23v interrupt enable tmrb 2/3 (over flow) 9fh inttbof3(tmrb3 over flow) inttbof2(tmrb2 over flow) itf3c itf3m2 itf3m1 itf3m0 itf2c itf2m2 itf2m1 itf2m0 rr / wrr / w 00000000 1: inttbof3 interrput level 1:inttbof2 interrput level
page 265 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 intertc interrupt enable intrtc a0h intrtc ? irtcc irtcm2 irtcm1 irtcm0 ???? rr / w ?? 0000 ???? 1: intrtc interrput level ?? intes0 interrupt enable serial 0 a1h inttx0 intrx0 itx0c itx0m2 itx0m1 itx0m0 irx0c irx0m2 irx0m1 irx0m0 rr / wrr / w 00000000 1: inttx0 interrput level 1: intrx0 interrput level intes1 interrupt enable serial 1 a2h inttx1 intrx1 itx1c itx1m2 itx1m1 itx1m0 irx1c irx1m2 irx1m1 irx1m0 rr / wrr / w 00000000 1: inttx1 interrput level 1: intrx1 interrput level intes2 interrupt enable serial 2 a3h inttx2 intrx2 itx2c itx2m2 itx2m1 itx2m0 irx0c irx2m2 irx2m1 irx2m0 rr / wrr / w 00000000 1: inttx2 interrput level 1: intrx2 interrput level intesbi0 interrupt enable sbi 0/1 a4h ? intsbi0 ???? isbi0c isbi0m2 isbi0m1 isbi0m0 ?? rr / w ???? 0000 ?? 1: intsbi0 interrput level intetc01 interrupt enable tc 0/1 a5h inttc1 inttc0 itc1c itc1m2 itc1m1 itc1m0 itc0c itc0m2 itc0m1 itc0m0 rr / wrr / w 00000000 1: inttc1 interrput level 1: inttc0 interrput level intetc23 interrupt enable tc 2/3 a6h inttc3 inttc2 itc3c itc3m2 itc3m1 itc3m0 itc2c itc2m2 itc2m1 itc2m0 rr / wrr / w 00000000 1: inttc3 interrput level 1: inttc2 interrput level
page 266 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 dma0v dma0 start vector 80h ?? dma0v5 dma0v4 dma0v3 dma0v2 dma0v1 dma0v0 ?? r/w ?? 000000 ?? dma0 start vector dma1v dma1 start vector 81h ?? dma1v5 dma1v4 dma1v3 dma1v2 dma1v1 dma1v0 ?? r/w ?? 000000 ?? dma1 start vector dma2v dma2 start vector 82h ?? dma2v5 dma2v4 dma2v3 dma2v2 dma2v1 dma2v0 ?? r/w ?? 000000 ?? dma2 start vector dma3v dma3 start vector 83h ?? dma3v5 dma3v4 dma3v3 dma3v2 dma3v1 dma3v0 ?? r/w ?? 000000 ?? dma3 start vector intclr interrupt clear control 88h (rmw instruc- tions are pro- hibited.) ?? clrv5 clrv4 clrv3 clrv2 clrv1 clrv0 ?? w ?? 000000 ?? interrupt vector dmar dma software request register 89h (rmw instruc- tions are pro- hibited.) ???? dmar3 dmar2 dmar1 dmar0 ???? r/w ???? 0000 ???? 1: dma software request dmab dma burst register 8ah ???? dmab3 dmab2 dmab1 dmab0 ???? r/w ???? 0000 ???? 1: dma burst request iimc interrupt input mode control 8ch (rmw instruc- tions are pro- hibited.) ????? i0edge i0le ? w 00000000 always write ?0?. ???? int0 edge 0: rising 1: falling int0 mode 0: edge 1: level ?
page 267 2007-10-10 tmp91fu62 (4) clock control symbol name address 7 6 5 4 3 2 1 0 syscr0 system clock control register 0 e0h xen xten rxen rxten rsysck wuef prck1 ? r/w ? 1010000? high- frequency oscillator 0:stop 1:oscilla- tion low- frequency oscillator 0:stop 1:oscilla- tion high- frequency oscillator (fc) after release of stop mode 0:stop 1:oscilla- tion low- frequency oscillator (fs) after release of stop mode 0:stop 1:oscilla- tion selects clock after release of stop mode 0:fc 1:fs warm-up timer con- trol 0 write: don't care 1 write: start warm-up 0 read: end warm- up 1 read: do not end warm-up select prescaler clock 0:f fph 1:fc/16 ? syscr1 system clock control register 1 e1h ? ? ? ? sysck gear2 gear2 gear2 ???? r / w ????0000 ???? select sys- tem clock 0: fc 1: fs select gear value of high frequency (fc) 000:fc 001:fc/2 010:fc/4 011:fc/8 100:fc/16 101:reserved 110:reserved 111:reserved syscr2 system clock control register 1 e2h ? scosel wuptm1 wuptm0 haltm1 haltm0 ? drve ?r / w? r / w ?01011?0 ? select scout 0:fs 1:f sys select warm-up time for oscillator 00:2 18 /inputted fre- quency 01:2 8 /inputted frequency 10:2 14 /inputted fre- quency 11:2 16 /inputted fre- quency halt mode 00:reserved 01:stop mode 10:idle1 mode 11:idle2 mode ? pin state control in stop mode 0: i/o off 1:remains the state before halt emccr0 emc control register 0 e3h p r o t e c t??????? rr / w 00100011 protect flag 0:off 1:on write "0". write "1". write "0". write "0". write "0". write "1". write "1". emccr1 emc control register 1 e4h protect off by writing "1fh". protect on by writing except "1fh".
page 268 2007-10-10 tmp91fu62 (5) 8-bit timer symbol name address 7 6 5 4 3 2 1 0 ta01run 8-bit timer run 100h ta0rde ? ? ? i2ta01 ta01prun ta1run ta0run r/w ? ? ? r/w 0???0000 double buffer 0: disable 1: enable ??? idle2 0: stop 1: operate tmra01 prescaler up counter (uc1) up counter (uc0) 0: stop and clear 1: run (count up) ta0reg 8-bit timer register 0 102h (rmw instruc- tions are pro- hibited.) ? w 0 ta1reg 8-bit timer register 1 103h (rmw instruc- tions are pro- hibited.) ? w 0 ta01mod 8-bit timer source clk & mode 104h ta01m1 ta01m0 pwm01 pwm00 ta1clk1 ta1clk0 ta0clk1 ta0clk0 r/w 00000000 operation mode 00: 8-bit timer mode 01: 16-bit timer mode 10: 8-bit ppg mode 11: 8-bit pwm mode pwm cycle 00: reserved 01: 2 6 10: 2 7 11: 2 8 input clock for tmra1 00: ta0trg 01: t1 10: t16 11: t256 input clock for tmra0 00: ta0in pin 01: t1 10: t4 11: t16 ta1ffcr 8-bit timer frip-flop control 105h ? ? ? ? ta1ffc1 ta1ffc0 ta1ffie ta1ffis ???? r / w ????1100 ???? 00: invert ta1ff 01: set ta1ff 10: clear ta1ff 11: don?t care ta1ff control for inversion 0: disable 1: enable ta1ff inversion select 0: tmra0 1: tmra1
page 269 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 ta45run 8-bit timer run 110h ta4rde ? ? ? i2ta45 ta45prun ta5run ta4run r/w ? ? ? r/w 0???0000 double buffer 0: disable 1: enable ??? idle2 0: stop 1: operate tmra45 prescaler up counter (uc5) up counter (uc4) 0: stop and clear 1: run (count up) ta4reg 8-bit timer register 0 112h (rmw instruc- tions are pro- hibited.) ? w 0 ta5reg 8-bit timer register 1 113h (rmw instruc- tions are pro- hibited.) ? w 0 ta45mod 8-bit timer source clk & mode 114h ta45m1 ta45m0 pwm41 pwm40 ta5clk1 ta5clk0 ta4clk1 ta4clk0 r/w 00000000 operation mode 00: 8-bit timer mode 01: 16-bit timer mode 10: 8-bit ppg mode 11: 8-bit pwm mode pwm cycle 00: reserved 01: 2 6 10: 2 7 11: 2 8 input clock for tmra5 00: ta4trg 01: t1 10: t16 11: t256 input clock for tmra4 00: ta4in pin 01: t1 10: t4 11: t16 ta5ffcr 8-bit timer frip-flop control 115h ? ? ? ? ta5ffc1 ta5ffc0 ta5ffie ta5ffis ???? r / w ????1100 ???? 00: invert ta5ff 01: set ta5ff 10: clear ta5ff 11: don?t care ta5ff control for inversion 0: disable 1: enable ta5ff inversion select 0: tmra4 1: tmra5
page 270 2007-10-10 tmp91fu62 (6) 16-bit timer symbol name address 7 6 5 4 3 2 1 0 tb0run 16-bit timer control 180h tb0rde ? ? ? i2tb0 tb0prun ? tb0run r/w ? ? r/w ? r/w 00??00?0 double buffer 0: disable 1: enable always write 0. ?? idle2 0: stop 1: operate tmrb0 prescaler ? up counter (uc0) 0: stop and clear 1: run (count up) tb0mod 16-bit timer source clk & mode 182h (rmw instruc- tions are pro- hibited.) tb0ct1 tb0et1 tb0cp0i tb0cpm1 tb0cpm0 tb0cle tb0clk1 tb0clk0 r/w w* r/w 00100000 tb0ff1 inversion trigger 0: trigger disable 1: trigger enable software capture control 0: software capture 1: unde- fined capture timing 00: disable int5 occurs at rising edge 01: tb0in0 tb0in1 int5 occurs at rising edge 10: tb0in0 tb0in0 int5 occurs at falling edge 11: ta1out ta1out int5 occurs at rising edge up counter control 0: clear disable 1: clear enable tmrb0 input clock select 00: tb0in0 pin input 01: t1 10: t4 11: t16 invert when uc0 is loaded into tb0cp1h/l invert when uc0 matches with tb0rg1h/l tb0ffcr 16-bit timer frip-flop control 183h (rmw instruc- tions are pro- hibited.) tb0ff1c1 tb0ff1c0 tb0c1t1 tb0c0t1 tb0e1t1 tb0e0t1 tb0ff0c1 tb0ff0c0 w* r/w w* 11000011 tb0ff1 control 00: invert 01: set 10: clear 11: don?t care note: always read as 11. tb0ff0 inversion trigger 0: disable 1: enable tb0ff0 control 00: invert 01: set 10: clear 11: don?t care note: always read as 11. invert when uc0 is loaded into tb0cp1h/l. invert when uc0 is loaded into tb0cp0h/l. invert when uc0 matches tb0rg1h/l. invert when uc0 matches tb0rg0h/l. tb0rg0l 16-bit timer register 0l 188h (rmw instruc- tions are pro- hibited.) ? w undefined tb0rg0h 16-bit timer register 0h 189h (rmw instruc- tions are pro- hibited.) ? w undefined tb0rg1l 16-bit timer register 1l 18ah (rmw instruc- tions are pro- hibited.) ? w undefined tb0rg1h 16-bit timer register 1h 18bh (rmw instruc- tions are pro- hibited.) ? w undefined tb0cp0l capture register 0l 18ch ? r undefined tb0cp0h capture register 0h 18dh ? r undefined tb0cp1l capture register 1l 18eh ? r undefined tb0cp1h capture register 1h 18fh ? r undefined
page 271 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 tb1run 16-bit timer control 190h tb1rde ? ? ? i2tb1 tb1prun ? tb1run r/w ? ? r/w ? r/w 00??00?0 double buffer 0: disable 1: enable always write 0. ?? idle2 0: stop 1: operate tmrb1 prescaler ? up counter (uc1) 0: stop and clear 1: run (count up) tb1mod 16-bit timer source clk & mode 192h (rmw instruc- tions are pro- hibited.) tb1ct1 tb1et1 tb1cp0i tb1cpm1 tb1cpm0 tb1cle tb1clk1 tb1clk0 r/w w* r/w 00100000 tb1ff1 inversion trigger 0: trigger disable 1: trigger enable software capture control 0: software capture 1: unde- fined capture timing 00: disable int7 occurs at rising edge 01: tb1in0 tb1in1 int7 occurs at rising edge 10: tb1in0 tb1in0 int7 occurs at falling edge 11: ta1out ta1out int7 occurs at rising edge up counter control 0: clear disable 1: clear enable tmrb1 input clock select 00: tb1in0 pin input 01: t1 10: t4 11: t16 invert when uc1 is loaded into tb1cp1h/l invert when uc1 matches with tb1rg1h/l tb1ffcr 16-bit timer frip-flop control 193h (rmw instruc- tions are pro- hibited.) tb1ff1c1 tb1ff1c0 tb1c1t1 tb1c0t1 tb1e1t1 tb1e0t1 tb1ff0c1 tb1ff0c0 w* r/w w* 11000011 tb1ff1 control 00: invert 01: set 10: clear 11: don?t care note: always read as 11. tb1ff0 inversion trigger 0: disable 1: enable tb1ff0 control 00: invert 01: set 10: clear 11: don?t care note: always read as 11. invert when uc1 is loaded into tb1cp1h/l. invert when uc1 is loaded into tb1cp0h/l. invert when uc1 matches tb1rg1h/l. invert when uc1 matches tb1rg0h/l. tb1rg0l 16-bit timer register 0l 198h (rmw instruc- tions are pro- hibited.) ? w undefined tb1rg0h 16-bit timer register 0h 199h (rmw instruc- tions are pro- hibited.) ? w undefined tb1rg1l 16-bit timer register 1l 19ah (rmw instruc- tions are pro- hibited.) ? w undefined tb1rg1h 16-bit timer register 1h 19bh (rmw instruc- tions are pro- hibited.) ? w undefined tb1cp0l capture register 0l 19ch ? r undefined tb1cp0h capture register 0h 19dh ? r undefined tb1cp1l capture register 1l 19eh ? r undefined tb1cp1h capture register 1h 19fh ? r undefined
page 272 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 tb2run 16-bit timer control 1a0h tb2rde ? ? ? i2tb2 tb2prun ? tb2run r/w ? ? r/w ? r/w 00??00?0 double buffer 0: disable 1: enable always write 0. ?? idle2 0: stop 1: operate tmrb2 prescaler ? up counter (uc2) 0: stop and clear 1: run (count up) tb2mod 16-bit timer source clk & mode 1a2h (rmw instruc- tions are pro- hibited.) tb2ct1 tb2et1 tb2cp0i tb2cpm1 tb2cpm0 tb2cle tb2clk1 tb2clk0 r/w w* r/w 00100000 tb2ff1 inversion trigger 0: trigger disable 1: trigger enable software capture control 0: software capture 1: unde- fined capture timing 00: disable int1 occurs at rising edge 01: tb2in0 tb2in1 int1 occurs at rising edge 10: tb2in0 tb2in0 int1 occurs at falling edge 11: ta1out ta1out int1 occurs at rising edge up counter control 0: clear disable 1: clear enable tmrb2 input clock select 00: tb2in0 pin input 01: t1 10: t4 11: t16 invert when uc2 is loaded into tb2cp1h/l invert when uc2 matches with tb2rg1h/l tb2ffcr 16-bit timer frip-flop control 1a3h (rmw instruc- tions are pro- hibited.) tb2ff1c1 tb2ff1c0 tb2c1t1 tb2c0t1 tb2e1t1 tb2e0t1 tb2ff0c1 tb2ff0c0 w* r/w w* 11000011 tb2ff1 control 00: invert 01: set 10: clear 11: don?t care note: always read as 11. tb2ff0 inversion trigger 0: disable 1: enable tb2ff0 control 00: invert 01: set 10: clear 11: don?t care note: always read as 11. invert when uc2 is loaded into tb2cp1h/l. invert when uc2 is loaded into tb2cp0h/l. invert when uc2 matches tb2rg1h/l. invert when uc2 matches tb2rg0h/l. tb2rg0l 16-bit timer register 0l 1a8h (rmw instruc- tions are pro- hibited.) ? w undefined tb2rg0h 16-bit timer register 0h 1a9h (rmw instruc- tions are pro- hibited.) ? w undefined tb2rg1l 16-bit timer register 1l 1aah (rmw instruc- tions are pro- hibited.) ? w undefined tb2rg1h 16-bit timer register 1h 1abh (rmw instruc- tions are pro- hibited.) ? w undefined tb2cp0l capture register 0l 1ach ? r undefined tb2cp0h capture register 0h 1adh ? r undefined tb2cp1l capture register 1l 1aeh ? r undefined tb2cp1h capture register 1h 1afh ? r undefined
page 273 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 tb3run 16-bit timer control 1b0h tb3rde ? ? ? i2tb3 tb3prun ? tb3run r/w ? ? r/w ? r/w 00??00?0 double buffer 0: disable 1: enable always write 0. ?? idle2 0: stop 1: operate tmrb3 prescaler ? up counter (uc3) 0: stop and clear 1: run (count up) tb3mod 16-bit timer source clk & mode 1b2h (rmw instruc- tions are pro- hibited.) tb3ct1 tb3et1 tb3cp0i tb3cpm1 tb3cpm0 tb3cle tb3clk1 tb3clk0 r/w w* r/w 00100000 tb3ff1 inversion trigger 0: trigger disable 1: trigger enable software capture control 0: software capture 1: unde- fined capture timing 00: disable int3 occurs at rising edge 01: tb3in0 tb3in1 int3 occurs at rising edge 10: tb3in0 tb3in0 int3 occurs at falling edge 11: reserved up counter control 0: clear disable 1: clear enable tmrb3 input clock select 00: tb3in0 pin input 01: t1 10: t4 11: t16 invert when uc3 is loaded into tb3cp1h/l invert when uc3 matches with tb3rg1h/l tb3ffcr 16-bit timer frip-flop control 1b3h (rmw instruc- tions are pro- hibited.) tb3ff1c1 tb3ff1c0 tb3c1t1 tb3c0t1 tb3e1t1 tb3e0t1 tb3ff0c1 tb3ff0c0 w* r/w w* 11000011 tb3ff1 control 00: invert 01: set 10: clear 11: don?t care note: always read as 11. tb3ff0 inversion trigger 0: disable 1: enable tb3ff0 control 00: invert 01: set 10: clear 11: don?t care note: always read as 11. invert when uc3 is loaded into tb3cp1h/l. invert when uc3 is loaded into tb3cp0h/l. invert when uc3 matches tb3rg1h/l. invert when uc3 matches tb3rg0h/l. tb3rg0l 16-bit timer register 0l 1b8h (rmw instruc- tions are pro- hibited.) ? w undefined tb3rg0h 16-bit timer register 0h 1b9h (rmw instruc- tions are pro- hibited.) ? w undefined tb3rg1l 16-bit timer register 1l 1bah (rmw instruc- tions are pro- hibited.) ? w undefined tb3rg1h 16-bit timer register 1h 1bbh (rmw instruc- tions are pro- hibited.) ? w undefined tb3cp0l capture register 0l 1bch ? r undefined tb3cp0h capture register 0h 1bdh ? r undefined tb3cp1l capture register 1l 1beh ? r undefined tb3cp1h capture register 1h 1bfh ? r undefined
page 274 2007-10-10 tmp91fu62 (7) uart/sio symbol name address 7 6 5 4 3 2 1 0 sc0buf serial channel 0 buffer 200h (rmw instruc- tions are pro- hibited.) rb7 / tb7 rb6 / tb6 rb5 / tb5 rb4 / tb4 rb3 / tb3 rb2 / tb2 rb1 / tb1 rb0 / tb0 r (receiving) / w (transmission) undefined sc0cr serial channel 0 control 201h (rmw instruc- tions are pro- hibited.) rb8 even pe oerr perr ferr sclks ioc r r/w r (cleared to "0" when read) r/w undefined 0 0 0 0 0 0 0 received data bit8 parity 0: odd 1: even parity addition 0: disable 1: enable overrun error flag 0: unde- tect error 1: detect error parity error flag 0: unde- tect error 1: detect error framing error flag 0: unde- tect error 1: detect error edge selection for sclk pin (i/o mode) 0: sclk 1: sclk edge selection for sclk pin (i/o mode) 0: sclk 1: sclk sc0mod0 serial channel 0 mode 0 202h tb8 ctse rxe wu sm1 sm0 sc1 sc0 r/w 00000000 transmis- sion data bit8 hand- shake function 0: disable 1: enable receive function 0: disable 1: enable wakeup function 0: disable 1: enable serial transmission mode 00: i/o interface mode 01: 7-bit uart mode 10: 8-bit uart mode 11: 9-bit uart mode serial transmission clock (uart) 00: timer ta0trg 01: baud rate generator 10: internal clock f sys 11: external clock (sclk input) br0cr baud ratel control 203h ? br0adde br0ck1 br0ck0 br0s3 br0s2 br0s1 br0s0 r/w 00000000 always write 0. + (16 - k)/ 16 division 0: disable 1: enable input clock selection for baud rate generator 00: t0 01: t2 10: t8 11: t32 setting of the divided frequency ?n? br0add serial channel 0 k setting register 204h ? ? ? ? br0k3 br0k2 br0k1 br0k0 ???? r / w ????0000 ???? sets frequency divisor ?k? (divided by n + (16 - k)/16) sc0mod1 serial channel 0 mode 1 205h i2s0 fdpx0 ? ? ? ? ? ? r / w ?????? 00?????? idle2 0: stop 1: run duplex 0: half 1: full ??????
page 275 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 sc1buf serial channel 1 buffer 208h (rmw instruc- tions are pro- hibited.) rb7 / tb7 rb6 / tb6 rb5 / tb5 rb4 / tb4 rb3 / tb3 rb2 / tb2 rb1 / tb1 rb0 / tb0 r (receiving) / w (transmission) undefined sc1cr serial channel 1 control 209h (rmw instruc- tions are pro- hibited.) rb8 even pe oerr perr ferr sclks ioc r r/w r (cleared to "0" when read) r/w undefined 0 0 0 0 0 0 0 received data bit8 parity 0: odd 1: even parity addition 0: disable 1: enable overrun error flag 0: unde- tect error 1: detect error parity error flag 0: unde- tect error 1: detect error framing error flag 0: unde- tect error 1: detect error edge selection for sclk pin (i/o mode) 0: sclk 1: sclk edge selection for sclk pin (i/o mode) 0: sclk 1: sclk sc1mod0 serial channel 1 mode 0 20ah tb8 ctse rxe wu sm1 sm0 sc1 sc0 r/w 00000000 transmis- sion data bit8 hand- shake function 0: disable 1: enable receive function 0: disable 1: enable wakeup function 0: disable 1: enable serial transmission mode 00: i/o interface mode 01: 7-bit uart mode 10: 8-bit uart mode 11: 9-bit uart mode serial transmission clock (uart) 00: timer ta0trg 01: baud rate generator 10: internal clock f sys 11: external clock (sclk input) br1cr baud ratel control 20bh ? br1adde br1ck1 br1ck0 br1s3 br1s2 br1s1 br1s0 r/w 00000000 always write ?0?. + (16 - k)/ 16 division 0: disable 1: enable input clock selection for baud rate generator 00: t0 01: t2 10: t8 11: t32 setting of the divided frequency ?n? br1add serial channel 1 k setting register 20ch ? ? ? ? br1k3 br1k2 br1k1 br1k0 ???? r / w ????0000 ???? sets frequency divisor ?k? (divided by n + (16 - k)/16) sc1mod1 serial channel 1 mode 1 20dh i2s1 fdpx1 ? ? ? ? ? ? r / w ?????? 00?????? idle2 0: stop 1: run duplex 0: half 1: full ??????
page 276 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 sc2buf serial channel 2 buffer 210h (rmw instruc- tions are pro- hibited.) rb7 / tb7 rb6 / tb6 rb5 / tb5 rb4 / tb4 rb3 / tb3 rb2 / tb2 rb1 / tb1 rb0 / tb0 r (receiving) / w (transmission) undefined sc2cr serial channel 2 control 211h (rmw instruc- tions are pro- hibited.) rb8 even pe oerr perr ferr sclks ioc r r/w r (cleared to "0" when read) r/w undefined 0 0 0 0 0 0 0 received data bit8 parity 0: odd 1: even parity addition 0: disable 1: enable overrun error flag 0: unde- tect error 1: detect error parity error flag 0: unde- tect error 1: detect error framing error flag 0: unde- tect error 1: detect error edge selection for sclk pin (i/o mode) 0: sclk 1: sclk edge selection for sclk pin (i/o mode) 0: sclk 1: sclk sc2mod0 serial channel 2 mode 0 212h tb8 ctse rxe wu sm1 sm0 sc1 sc0 r/w 00000000 transmis- sion data bit8 hand- shake function 0: disable 1: enable receive function 0: disable 1: enable wakeup function 0: disable 1: enable serial transmission mode 00: i/o interface mode 01: 7-bit uart mode 10: 8-bit uart mode 11: 9-bit uart mode serial transmission clock (uart) 00: timer ta0trg 01: baud rate generator 10: internal clock f sys 11: external clock (sclk input) br2cr baud ratel control 213h ? br2adde br2ck1 br2ck0 br2s3 br2s2 br2s1 br2s0 r/w 00000000 always write ?0?. + (16 - k)/ 16 division 0: disable 1: enable input clock selection for baud rate generator 00: t0 01: t2 10: t8 11: t32 setting of the divided frequency ?n? br2add serial channel 2 k setting register 214h ? ? ? ? br2k3 br2k2 br2k1 br2k0 ???? r / w ????0000 ???? sets frequency divisor ?k? (divided by n + (16 - k)/16) sc2mod1 serial channel 2 mode 1 215h i2s2 fdpx2 ? ? ? ? ? ? r / w ?????? 00?????? idle2 0: stop 1: run duplex 0: half 1: full ??????
page 277 2007-10-10 tmp91fu62 (8) i 2 c bus interface symbol name address 7 6 5 4 3 2 1 0 sbi0cr1 serial bus interface control register 1 240h (rmw instruc- tions are pro- hibited.) bc2 bc1 bc0 ack ? sck2 sck1 sck0/ swrmon wr / w ?wr / w 0000?000 / 1 number of transferred bits 000: 8 001: 1 010: 2 011: 3 100: 4 101: 5 110: 6 111: 7 acknowl- edge clock 0: disable 1: enable ? at write internal serial clock selection and soft- ware reset monitor 000: 4 001: 5 010: 6 011: 7 100: 8 101: 9 110: 10 111:reserved at read 0: during software reset sbi0dbr sbi buffer register 241h (rmw instruc- tions are pro- hibited.) db7 db6 db5 db4 db3 db2 db1 db0 r (receiving) / w (transmission) undefined i2c0ar i 2 c bus address register 242h (rmw instruc- tions are pro- hibited.) sa6 sa5 sa4 sa3 sa2 sa1 sa0 als w 00000000 slave address selection for when device is operating as slave device address recognition 0: enable 1: disable when read sbi0sr serial bus interface status register 243h (rmw instruc- tions are pro- hibited.) mst trx bb pin al/ sbim1 aas/ sbim0 ad0/ swrst1 lrb/ swrst0 r/w 00010000 0: slave 1: master 0:receiver 1:transmit bus status monitor 0: free 1: busy[ intsbi request monitor 0: request 1: cancel arbitration lost detection monitor 1: detect slave address match detection monitor 1:detect general call detection 1: detect last receive bit monitor 0: ?0? 1: ?1? when write sbi0cr2 serial bus interface control register 2 start/stop condition 0: start condition 1: stop condition cancel intsbi interrupt request 0: ? 1: cancel serial bus interface operating mode selec- tion 00: port mode 01: reserved 10: i 2 c bus mode 11: reserved software reset generate write ?10? and ?01?, then an internal reset signal is generated. sbi0br serial bus interface baud rate register 244h (rmw instruc- tions are pro- hibited.) ?i2sbi0? ? ? ? ? ? wr/w?????r/w 00?????0 always write ?0? operation in idle2 mode 0: stop 1: operate ????? always write ?0? sbi0cr0 serial bus interface control register 0 247h (rmw instruc- tions are pro- hibited.) s b i 0 e n??????? r/w r 00000000 sbi operation 0: disable 1: enable always read "0".
page 278 2007-10-10 tmp91fu62 (9) ad converter symbol name address 7 6 5 4 3 2 1 0 adccr1 ad control register 1 2b0h adrs amd ainen sain r/w 00000000 ad con- version start 0: - 1: ad con- version start ad operating mode 00: ad operation disable 01: single mode 10: reserved 11: repeat mode analog input con- trol 0: disable 1: enable analog input channel select 0000: an0 0100: an4 1000: an8 1100: an12 0001: an1 0101: an5 1001: an9 1101: an13 0010: an2 0110: an6 1010: an10 1110: an14 0011: an3 0111: an7 1011: an11 1111: an15 adccr2 ad control register 2 2b1h (rmw instruc- tions are pro- hibited.) eocf adbf rsel i2ad ack rr / w 00001100 ad con- version end flag 0:before or during conversion 1: conver- sion com- pleted ad con- version busy flag 0: during stop of ad conversion 1: during ad con- version storing of an ad conver- sion result 0: 10bit mode 1: 8bit mode idle2 control 0:stop 1:opera- tion ad conversion time select 1010: 78 / fc [s] 1011: 156 / fc [s] 1100: 312 / fc [s] 1101: 624 / fc [s] 1110: 1248 / fc [s] adcdrl ad result register l 2b2h ad07 ad06 ad05 ad04 ad03 ad02 ad01 ad00 r 00000000 adcdrh when 10-bit storing mode ad result register h 2b3h ??????a d 0 9a d 0 8 r 00000000 adcdrh when 8-bit storing mode ad09 ad08 ad07 ad06 ad05 ad04 ad03 ad02 r 00000000
page 279 2007-10-10 tmp91fu62 (10) watchdog timer symbol name address 7 6 5 4 3 2 1 0 wdmod wdt mode register 300h wdte wdtp1 wdtp0 ? ? i2wdt rescr ? r/w ? ? r/w 000??000 wdt control 1: enable select detecting time 00: 2 15 /f sys 01: 2 17 /f sys 10: 2 19 /f sys 11: 2 21 /f sys ?? idle2 0: stop 1: operate 1: inter- mally con- nects wdt out to the reset pin always write ?0?. wdcr wdt control 301h (rmw instruc- tions are pro- hibited.) ? w ? b1h: wdt disable code 4eh: wdt clear code (11) special timer for clock symbol name address 7 6 5 4 3 2 1 0 rtccr rtc control register 310h ? ? ? ? ? rtcsel1 rtcsel0 rtcrun r / w???? r / w 0????000 always write ?0?. ???? 00: 2 14 /fs 01: 2 13 /fs 10: 2 12 /fs 11: 2 11 /fs 0: stop & clear 1: count
page 280 2007-10-10 tmp91fu62 (12) program patch logic symbol name address 7 6 5 4 3 2 1 0 romcmp00 address compare register 00 400h (rmw instruc- tions are pro- hibited.) romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? w? 0000000? target rom address (lower 7 bits) ? romcmp01 address compare register 01 401h (rmw instruc- tions are pro- hibited.) romc15 romc14 romc13 romc12 romc11 romc10 romc09 romc08 w 00000000 target rom address (middle 8 bits) romcmp02 address compare register 02 402h (rmw instruc- tions are pro- hibited.) romc23 romc22 romc21 romc20 romc19 romc18 romc17 romc16 w 00000000 target rom address (upper 8 bits) romsub0l address substitution register 0l 404h (rmw instruc- tions are pro- hibited.) roms07 roms06 roms05 roms04 roms03 roms02 roms01 roms00 w 00000000 patch code (lower 8 bits) romsub0h address substitution register 0h 405h (rmw instruc- tions are pro- hibited.) roms15 roms14 roms13 roms12 roms11 roms10 roms09 roms08 w 00000000 patch code (upper 8 bits) romcmp10 address compare register 10 408h (rmw instruc- tions are pro- hibited.) romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? w? 0000000? target rom address (lower 7 bits) ? romcmp11 address compare register 11 409h (rmw instruc- tions are pro- hibited.) romc15 romc14 romc13 romc12 romc11 romc10 romc09 romc08 w 00000000 target rom address (middle 8 bits) romcmp12 address compare register 12 40ah (rmw instruc- tions are pro- hibited.) romc23 romc22 romc21 romc20 romc19 romc18 romc17 romc16 w 00000000 target rom address (upper 8 bits) romsub1l address substitution register 1l 40ch (rmw instruc- tions are pro- hibited.) roms07 roms06 roms05 roms04 roms03 roms02 roms01 roms00 w 00000000 patch code (lower 8 bits) romsub1h address substitution register 1h 40dh (rmw instruc- tions are pro- hibited.) roms15 roms14 roms13 roms12 roms11 roms10 roms09 roms08 w 00000000 patch code (upper 8 bits)
page 281 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 romcmp20 address compare register 20 410h (rmw instruc- tions are pro- hibited.) romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? w? 0000000? target rom address (lower 7 bits) ? romcmp21 address compare register 21 411h (rmw instruc- tions are pro- hibited.) romc15 romc14 romc13 romc12 romc11 romc10 romc09 romc08 w 00000000 target rom address (middle 8 bits) romcmp22 address compare register 22 412h (rmw instruc- tions are pro- hibited.) romc23 romc22 romc21 romc20 romc19 romc18 romc17 romc16 w 00000000 target rom address (upper 8 bits) romsub2l address substitution register 2l 414h (rmw instruc- tions are pro- hibited.) roms07 roms06 roms05 roms04 roms03 roms02 roms01 roms00 w 00000000 patch code (lower 8 bits) romsub2h address substitution register 2h 415h (rmw instruc- tions are pro- hibited.) roms15 roms14 roms13 roms12 roms11 roms10 roms09 roms08 w 00000000 patch code (upper 8 bits) romcmp30 address compare register 30 418h (rmw instruc- tions are pro- hibited.) romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? w? 0000000? target rom address (lower 7 bits) ? romcmp31 address compare register 31 419h (rmw instruc- tions are pro- hibited.) romc15 romc14 romc13 romc12 romc11 romc10 romc09 romc08 w 00000000 target rom address (middle 8 bits) romcmp32 address compare register 32 41ah (rmw instruc- tions are pro- hibited.) romc23 romc22 romc21 romc20 romc19 romc18 romc17 romc16 w 00000000 target rom address (upper 8 bits) romsub3l address substitution register 3l 41ch (rmw instruc- tions are pro- hibited.) roms07 roms06 roms05 roms04 roms03 roms02 roms01 roms00 w 00000000 patch code (lower 8 bits) romsub3h address substitution register 3h 41dh (rmw instruc- tions are pro- hibited.) roms15 roms14 roms13 roms12 roms11 roms10 roms09 roms08 w 00000000 patch code (upper 8 bits)
page 282 2007-10-10 tmp91fu62 symbol name address 7 6 5 4 3 2 1 0 romcmp40 address compare register 40 420h (rmw instruc- tions are pro- hibited.) romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? w? 0000000? target rom address (lower 7 bits) ? romcmp41 address compare register 41 421h (rmw instruc- tions are pro- hibited.) romc15 romc14 romc13 romc12 romc11 romc10 romc09 romc08 w 00000000 target rom address (middle 8 bits) romcmp42 address compare register 22 422h (rmw instruc- tions are pro- hibited.) romc23 romc22 romc21 romc20 romc19 romc18 romc17 romc16 w 00000000 target rom address (upper 8 bits) romsub4l address substitution register 4l 424h (rmw instruc- tions are pro- hibited.) roms07 roms06 roms05 roms04 roms03 roms02 roms01 roms00 w 00000000 patch code (lower 8 bits) romsub4h address substitution register 4h 425h (rmw instruc- tions are pro- hibited.) roms15 roms14 roms13 roms12 roms11 roms10 roms09 roms08 w 00000000 patch code (upper 8 bits) romcmp50 address compare register 50 428h (rmw instruc- tions are pro- hibited.) romc07 romc06 romc05 romc04 romc03 romc02 romc01 ? w? 0000000? target rom address (lower 7 bits) ? romcmp51 address compare register 51 429h (rmw instruc- tions are pro- hibited.) romc15 romc14 romc13 romc12 romc11 romc10 romc09 romc08 w 00000000 target rom address (middle 8 bits) romcmp52 address compare register 52 42ah (rmw instruc- tions are pro- hibited.) romc23 romc22 romc21 romc20 romc19 romc18 romc17 romc16 w 00000000 target rom address (upper 8 bits) romsub5l address substitution register 5l 42ch (rmw instruc- tions are pro- hibited.) roms07 roms06 roms05 roms04 roms03 roms02 roms01 roms00 w 00000000 patch code (lower 8 bits) romsub5h address substitution register 5h 42dh (rmw instruc- tions are pro- hibited.) roms15 roms14 roms13 roms12 roms11 roms10 roms09 roms08 w 00000000 patch code (upper 8 bits)
page 283 2007-10-10 tmp91fu62 16. i/o port equivalent-circuit diagrams ? how to read circuit diagrams the circuit diagrams in this chapter are drawn using the same gate symb ols as for the 74hcxx series stan- dard cmos logic ics. the signal named stop has a unique function. this si gnal goes active-high if the cpu sets the halt bit when the haltm[1:0] field in the syscr2 register is programmed to 01 (e.g., stop mode) and the drive enable (drve) bit in the same register is cleared. if the drve bit is set, the stop signal remains inactive (at logic 0). ? the input protection circuit has a resistor in the range of several tens to several hundreds of ohms. 16.1 equivalent circuit diagrams 1. p0, p1 2. p5 (an0 to an7), p6 (an8 to an15) 3. p40(scout), p41(txd2), p42(rxd2), p43(sclk2/cts2 ) v cc 1wvrwvfcvc p-ch +prwv1wvrwv +prwvfcvc 1wvrwvgpcdng stop +prwvgpcdng n-ch #pcnqikprwv ejcppgnugngev #pcnqikprwv v cc 1wvrwvfcvc p-ch +prwv1wvrwv +prwvfcvc 1wvrwvgpcdng stop +prwvgpcdng n-ch +prwv1wvrwv +p r wvgpcdng v cc 1wvrwvfcvc 1wvrwvgpcdng stop +prwvfcvc vcc 2tqitcoocdng rwnnwrtgukuvqt p-ch n-ch
page 284 2007-10-10 tmp91fu62 4. p75 (int0) 5. p32(wait /tb3out0), p33(tb3out1), p70(ta0in), p71(ta1out), p72, p73(ta4in), p74(ta5out), p80 to p87, p91(rxd0), p92(sclk0/cts0 ), p94(rxd1), p95(sclk1/cts1 ), pa0 to pa3, pb0 to pb2 6. p30(tb3in0/int3/sda0), p31(tb3in1 /int4/scl0), p90(txd0), p93(txd1) 7. p96 (xt1), p97 (xt2) +prwv1wvrwv uejokvvvtkiigt v cc 1wvrwvfcvc 1wvrwvgpcdng stop +prwvfcvc  p-ch n-ch v cc 1wvrwvfcvc p-ch +prwv1wvrwv +prwvfcvc 1wvrwvgpcdng stop +p r wvgpcdng n - ch +prwv1wvrwv +p r wvgpcdng v cc 1wvrwvfcvc stop +prwvfcvc 1rgpftckp qwvrwvgpcdng  p-ch n-ch p96(xt1) p97(xt2) stop ^ vcc vcc +prwvfcvc 1wvrwvfcvc 1wvrwvgpcdng +prwvfcvc 1wvrwvfcvc 1wvrwvgpcdng .qyhtgswgpe[queknncvqtgpcdng +prwvgpcdng +prwvgpcdng %nqem 1ueknncvqtektewkv p-ch n-ch p-ch n-ch
page 285 2007-10-10 tmp91fu62 8. am0 to am1 9. reset 10. x1, x2 11. avcc, avss +prwv +prwv wdtout 4gugv 4gugvgpcdng 5ejokvvvtkiigt p-ch vcc x2 *kijhtgswgpe[ queknncvqtgpcdng 1ueknncvqtektewkv p - ch n - ch %n qe m  x1 a vcc vrefon a vss p - ch .cffgttgukuvqtu
page 286 2007-10-10 tmp91fu62 17. points to note and restrictions 17.1 notation a. the notation for built-in i/o registers is as follows register symbol e.g.) ta01run denotes bit ta0run of register ta01run. b. read-modify-write instructions an instruction in which the cpu reads data from memory and writes the data to the same memory loca- tion in one instruction. example 1: set 3, (ta01run) ... set bit3 of ta01run. example 2: inc 1, (100h) ... increment the data at 100h. ? examples of read-modify-write instructions on the tlcs-900 exchange instruction ex (mem), r arithmetic operations add (mem), r/# adc (mem), r/# sub (mem), r/# sbc (mem), r/# inc #3, (mem) dec #3, (mem) logic operations and (mem), r/# or (mem), r/# xor (mem), r/# bit manipulation operations stcf #3/a, (mem) res #3, (mem) set #3, (mem) chg #3, (mem) tset #3, (mem) rotate and shift operations rlc (mem) rrc (mem) rl (mem) rr (mem) sla (mem) sra (mem) sll (mem) srl (mem) rld (mem) rrd (mem) c. f osch , fc , fs , f fph , f sys and one state the clock frequency input on pins x1 and 2 is called f osch or fc. the clock selected by syscr1 is called f fph . the clock frequency give by f fph divided by 2 is called f sys . one cycle of f sys is referred to as one state.
page 287 2007-10-10 tmp91fu62 17.2 points of note a. am0 and am1 pins this pin is connected to th e dvcc pin. do not alter the level when the pin is active. b. emu0 pins open pins. c. halt mode (idle1) when idle1 mode (in which oscillator operati on only occurs) is used, set rtccr to 0 stop the special timer for clock befo re the halt instructions is executed. d. warm-up counter the warm-up counter operates when stop mode is re leased, even if the syst em is using an external oscillator. as a result a time equivalent to the warm -up time elapses between input of the release request and output of the system clock. e. programmable pull-up/pull-down resistances the programmable pull-up/pull-down resistor can be turned on/off by a prog ram when the ports are set for use as input ports. when the ports are set for use as output prts, they cannot be turned on/off by a program. the data registers (e.g., p4) are used to turn the pull-up/pull-down resistors on/off. consequently read-modify-write instru ctions are prohibited. f. watchdog timer the watchdog timer starts operation immediately after a reset is released. when the watchdog timer is not to be used, disable it. when the bus is released, neither internal memory nor internal i/o can be acce ssed. however, the inter- nal i/o continues to operate. hen ce the watchdog timer continues to ru n. therefore be careful about the bus releasing time and set the detection timer of watchdog timer. g. cpu (micro dma) only the lcd cr, r and ldc r, cr instructions can be used to access the control registers in the cpu (e.g., the transfer source address register (dmasn)). h. undefined sfr the value of an undefined bit in an sfr is undefined when read. i. pop sr instruction please execute the pop sr instruction during di condition. j. clocks for serial channels (sio) as for the serial channels sio0, si o1 and sio2, a baud rate generator is unavailable as an input clock of an i/o interface and a clock for a serial tran sfer if a prescaler clock is set to fc/16 when syscr0 is "1".
page 288 2007-10-10 tmp91fu62 18. package dimension unit: mm 21 40 41 60 61 80 0.5 0.08 0.22 0.05 1.25 typ. 20 lqfp80-p-1212-0.50e
page 289 2007-10-10 tmp91fu62 qfp80-p-1420-0.80b unit: mm
postscript this is a technical document that describes the oper ating functions and electrical specifications of the 16- bit microcontroller series tlcs-900/l1 (lsi). toshiba provides a variety of development tools an d basic software to enable efficient software development. these development tools have specifications that suppo rt advances in microcomputer hardware (lsi) and can be used extensively. both the hardware and soft ware are supported continuou sly with version updates. the recent advances in cmos ls i production technology have been phenomenal and microcomputer systems for lsi design are constantly being improved. the products described in this document may also be revised in the future. be sure to check the latest specifications before using. toshiba is developing highly integrated, high-performance microcomputers using advanced mos production technology and especially well proven cmos technology. we are prepared to meet the requests for custom packaging for a variety of application areas. we are confident that our products can satisfy your application needs now and in the future.